Webhooks integration
MeetStream pushes meeting lifecycle events to your endpoint as they happen. That is how teams move meetings into a CRM, Slack, a database, or an internal pipeline without polling the API.
What this integration gives you
- Lifecycle events POSTed to your endpoint in real time
- Events for bot joined, recording started, meeting ended, recording ready, and transcript ready
- Event-driven wiring into CRMs, Slack, databases, and internal pipelines
- No polling loop to build or maintain
- A clean trigger point for downstream automation
- Pairs with bring-your-own S3 so media lands in your bucket as events fire
What events you receive
Webhooks cover the meeting lifecycle. You get notified when the bot joins, when recording starts, when the meeting ends, when the recording is ready, and when the transcript is ready. Each event is POSTed to the endpoint you register, carrying the identifiers you need to fetch the associated media or transcript.
The value of an event stream is timing. Your system learns that a transcript is ready the moment it is ready, so the work that depends on it can start immediately. There is no interval to tune and no wasted requests checking for something that has not happened yet.
Wiring meetings into downstream systems
Webhooks are the connective tissue between a meeting and the rest of your stack. A recording ready event can trigger a job that stores the file and updates a record. A transcript ready event can kick off summarization, then write the summary into a CRM or post it to a Slack channel. The meeting ended event can close out state in your database.
Because the events are pushed, your integration is reactive rather than scheduled. You define what happens on each event, and MeetStream calls you when there is something to act on. This is what teams use to auto-update deal records, notify a channel when a call finishes, or feed transcripts into an internal analytics pipeline, all without a polling service running in the background.
- Recording ready to store media and update a record
- Transcript ready to summarize and enrich a CRM
- Meeting ended to close out session state
- Bot joined and recording started for live status tracking
How to connect
- Stand up an HTTPS endpoint that accepts POST requests.
- Register the endpoint as your webhook in the dashboard at app.meetstream.ai.
- Handle each event type and use the identifiers to fetch media or transcripts.
- Trigger your downstream actions: CRM updates, Slack messages, database writes, or pipeline jobs.
$ curl -X POST \
https://api.meetstream.ai/api/v1/bot \
-H "Authorization: Bearer $API_KEY" \
-d '{"url": "zoom.us/j/74648392"}'
Frequently asked questions
Which events does MeetStream send?
Lifecycle events across the meeting: bot joined, recording started, meeting ended, recording ready, and transcript ready. Each is POSTed to your endpoint with the identifiers you need to retrieve the related media or transcript.
Do I still need to poll the API?
No. That is the point of webhooks. MeetStream pushes events to your endpoint the moment they occur, so you react to them directly instead of running a polling loop to check for status changes.
How do teams use webhooks in practice?
Common patterns include updating a CRM record when a transcript is ready, posting to a Slack channel when a meeting ends, and writing recordings into a database or pipeline. The event is the trigger, and your handler decides what happens next.
Can webhooks work with my own storage?
Yes. Webhooks pair naturally with bring-your-own S3. Media is written to your bucket while events notify your systems, so you get both the file in your storage and the signal to act on it.
Connect it in an afternoon
One API to join, record, stream, and transcribe meetings across Zoom, Google Meet, and Microsoft Teams.