Webhook payloads
Sample payloads and headers sent by Distro Workflows webhooks.
Sample webhook payloads for different sources in Distro Workflows.
Distro sends JSON by HTTP POST to your configured webhook URL.
Payload shape depends on the source type and trigger.

Basics
All webhooks use the same envelope:
event: the trigger that fired the webhook (see Workflows).timestamp: ISO 8601 time when Distro built the payload. Retries reuse the payload.data: the event payload. Shape depends on source type.
Conventions:
Keys use
snake_case.data.source_typeis one of:router,click_router,booking_link,group_meeting_link,outbound_router.Submission-only triggers include
submissionandassignee; they omitbookingandattendees. Meeting triggers includebooking,assignee, andattendees; they omitsubmission.
Meeting details
Booking payloads also include location, in_person, and event_type. For an in-person meeting, use location as the meeting address; do not expect a conferencing URL. event_type, when present, contains id, title, and availability_mode.
For an Outbound Router, source_type is outbound_router, source_id identifies the router, and source_title contains its name. The booking envelope is the same as other meeting sources. Outbound attendees also include their role.
Payload examples
Triggered by Click Routers.
Triggered by Personal Booking Links.
Triggered by Group Meeting Links.
Operational notes
Last updated