Skip to navigation

In-Meeting Chat & Visuals

Read the chat, post messages, and show images through your bot
View as Markdown

MeetStream bots are participants, not just recorders: they can post in the chat, show visuals, and hand you the chat log afterwards.

Platform support

ZoomGoogle MeetMicrosoft Teams
Send chat (send_message)Yes, to everyoneYes, to everyoneYes, to everyone
Intro message (bot_message)Posted once after joiningPosted a few seconds after joiningPosted after joining
Show an image (send_image, bot_image_url)Yes, as the bot’s camera. Animated GIFs playYes, as the bot’s camera. Animated GIFs playYes, as the bot’s camera. Animated GIFs play
Read chat live (participant_events.chat_message webhook)Yes. to is everyone, the recipient’s name, or directYesYes. Every message is reported as to: "everyone"
Chat log after the callIn the participant events file (see below)get_chatsget_chats

The bot can only post and read chat where the meeting allows chat for it. If the organizer has turned chat off for the meeting (or for guests, when the bot joins as a guest), messages cannot be sent. See the capability matrix for everything else each platform supports.

Send a chat message (live)

curl -X POST "https://api.meetstream.ai/api/v1/bots/<BOT_ID>/send_message" \
-H "Authorization: Token <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{ "message": "The summary will be in #sales-notes after the call." }'

Response (200): { "status": "accepted", "bot_id": "...", "command": "sendmsg", "request_id": "..." }. CLI: meetstream bot send-message <id> <text>.

  • Up to 2,000 characters. Empty messages are rejected with 400.
  • Send once the bot is in the meeting (bot.inmeeting). While it waits in the lobby, or after it has left, you get 409 (Bot is not currently in a meeting.).
  • accepted means the bot received the command. Delivery into the meeting chat happens a moment later.

Show an image or GIF (live)

send_image displays an image as the bot’s video frame. Great for QR codes, “recording in progress” cards, or a bit of personality:

curl -X POST "https://api.meetstream.ai/api/v1/bots/<BOT_ID>/send_image" \
-H "Authorization: Token <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{ "img_url": "https://your-cdn.com/recording-notice.gif", "display_duration": 30 }'
FieldRules
img_urlA public https:// URL, up to 2,048 characters
imgInstead of img_url: the image as base64, up to about 5 MB
display_durationOptional. Seconds to show the image (up to 300), after which the bot goes back to its bot_image_url. Without it, the image stays until you send another

Set the bot’s presence at join time

Two create_bot fields shape how the bot shows up:

  • bot_message: a chat message posted automatically when the bot joins (“Hi! I’m recording this call for notes.”)
  • bot_image_url: a public https:// image (PNG, JPG, GIF or WebP) used as the bot’s camera picture, on every platform

Read the chat afterwards

On Google Meet and Microsoft Teams:

curl "https://api.meetstream.ai/api/v1/bots/<BOT_ID>/get_chats" \
-H "Authorization: Token <YOUR_API_KEY>"

The response includes session metadata plus the per-speaker message log, ready for sentiment analysis, question extraction, or CRM notes. It is available after the bot leaves: until then you get 202 (Manifest is still being processed...).

On Zoom, read chat messages from the participant events file: call GET /api/v1/bots/{bot_id}/detail and download participant_events.download_url, then read the entries with action chat_message. (get_chats returns 404 with Chats file not found for this bot for Zoom bots.)

To get chat live on every platform, use workspace webhook endpoints: they receive a participant_events.chat_message event for each message. See webhooks and events.

Rate limits

In-meeting commands (send_message, send_image, pause and resume) share a limit of 30 per minute per bot. Over the limit you get 429 with retry_after. On Google Meet, chat messages have their own, higher limit and are delivered in order.

Going further