Skip to main content

Event types

Subscribe to the events relevant to your integration. Each event includes a type string and a data object with event-specific fields.

meeting.completed

Fired when a meeting recording ends and the recording file is processed. This is typically the first event in the pipeline after a meeting finishes.
Payload
string
The unique meeting identifier. Use this to fetch the full meeting object via GET /meetings/:id.
string
The meeting title.
string
Platform where the meeting was recorded.
string
When the recording started.
string
When the recording ended.
integer
Duration in seconds.
integer
Number of identified participants.
object
Recording metadata including file_size_bytes and format.

transcript.ready

Fired when the transcript for a meeting has been generated. This typically occurs 1-3 minutes after meeting.completed, depending on the meeting length.
Payload
string
The meeting this transcript belongs to.
string
The transcript identifier. Use this to fetch the full transcript via GET /transcripts/:id.
string
Detected language (ISO 639-1).
integer
Duration of the transcribed audio.
integer
Total words in the transcript.
number
Overall transcription confidence score (0 to 1).
integer
Number of speaker-attributed segments.

summary.ready

Fired when a summary has been generated or regenerated. This typically occurs 15-30 seconds after transcript.ready.
Payload
string
The meeting this summary belongs to.
string
The summary identifier. Use this to fetch the full summary via GET /summaries/:id.
string
Summary format: structured, narrative, or bullet_points.
string
Language of the summary.
integer
Number of action items extracted.
integer
Number of key decisions identified.
boolean
true if this summary was produced by a regeneration request, false if it was the initial generation.

action_item.created

Fired when action items are extracted from a meeting. This event fires once per meeting and includes all action items identified in that meeting.
Payload
string
The meeting where these action items were identified.
string
Title of the meeting.
array
Array of action item summaries. Each includes id, title, assignee, due_date, and priority. Use the List action items endpoint for full details.

action_item.completed

Fired when an action item is marked as completed, either via the API or from the Mavio dashboard.
Payload
string
The completed action item identifier.
string
Title of the completed action item.
string
Name of the person who was assigned.
string
The meeting this action item came from.
string
Title of the meeting.
string
ISO 8601 timestamp of completion.
string
How the item was completed: api (via the API), dashboard (via the Mavio web app), or integration (via a connected integration like Slack).

Event timeline

For a typical meeting, events fire in this order:
If you only need to know when a meeting is fully processed, subscribe to summary.ready. By the time this event fires, the transcript, summary, and action items are all available.