Skip to main content

Documentation Index

Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

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

Internal eventTrigger path
meeting.completedRecall transcript fetch completes successfully for a recording.

Payload example

{
  "type": "meeting.completed",
  "object": "event",
  "data": {
    "recordingId": "rec_x8y7z6",
    "meetingId": "mt_4f3d2a",
    "status": "done"
  }
}

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 automation.
  • Store processed IDs before starting downstream tasks like meeting summaries or billing attribution.
Last modified on April 26, 2026