Skip to main content
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see Webhook Concepts.

Description

This event is triggered when a scheduled meeting is updated — for example, when it is rescheduled, cancelled, or a participant’s RSVP status changes (subordinate bubble-up).

Integration Details

  • Subscription Key: sch.meeting.updated
  • Use Case: Update local calendar entries or trigger follow-up tasks when a meeting status changes.
  • Related Events: sch.meeting.created

Trigger

  • Event Type: sch_meeting_updated
  • Source: Update of a record in the sch.meeting table, or bubble-up from subordinate changes to sch.meeting_participant or sch.meeting_file.
This event does not include an old field. Meeting history is tracked in the sch.meeting_history table. Use the Webhook Concepts page for more context.

Cross-Service References

  • Auth (auth.user): user_details on each participant provides an identity snapshot from the auth service.

Payload Example

Payload Type Showcase

Field Notes

  • location and additional_params are JSONB — shape varies by meeting configuration.
  • meta on participants is JSONB with provider-specific metadata.
  • user_details is a cross-service join to auth.user — provides the participant’s identity snapshot.
  • meeting_files are recordings or attachments linked to the meeting.
  • duration is a Postgres INTERVAL rendered as a string (e.g., "01:00:00").
  • Participant and file changes trigger bubble-up to the meeting root.