Skip to main content

meeting.completed

What this event means

meeting.completed is emitted when a meeting recording has completed and transcript processing has completed, so transcript data is available.

Webhook type

meeting.completed

Internal source mapping

Payload example

Delivery and idempotency handling

  • Use data.recordingId (and optionally data.meetingId) as the primary identifier.
  • Meeting completion can be retried by upstream processing; dedupe updates before running follow-up jobs.
  • Store processed IDs before starting downstream tasks like meeting summaries or billing attribution.
Last modified on July 30, 2026