Twilio studio webhook events
Twilio sends 3 studio events: com.twilio.studio.flow.execution.started, com.twilio.studio.flow.execution.ended and com.twilio.studio.flow.step.ended. 2 have sample payloads.
Twilio has two systems that send you webhooks. Messaging, Voice and other products call a URL you set on a number or resource, with form parameters and no event type field. Event Streams sends JSON CloudEvents with a type. The events list names Event Streams types and Conversations (classic) actions, because a status callback has no event name to list. SendGrid's email events are separate: see SendGrid webhooks.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
com.twilio.studio.flow.execution.started
documented No payload yet
com.twilio.studio.flow.execution.started Studio flow execution starts
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource studio
No payload yet.
com.twilio.studio.flow.execution.ended
documented from Twilio docs (example)
com.twilio.studio.flow.execution.ended Studio flow execution ends
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource studio
{
"specversion": "1.0",
"type": "com.twilio.studio.flow.execution.ended",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Studio.FlowExecutionEvent/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.studio.flow.execution.ended |
Full schema: 17 fields.
From Twilio docs
-
Content type
application/json
com.twilio.studio.flow.step.ended
documented from Twilio docs (example)
com.twilio.studio.flow.step.ended Studio flow step ends
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource studio
{
"specversion": "1.0",
"type": "com.twilio.studio.flow.step.ended",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Studio.FlowStepEvent/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.studio.flow.step.ended |
Full schema: 16 fields.
From Twilio docs
-
Content type
application/json
Route Twilio events by type.
Event Gateway receives every Twilio delivery and filters and routes it by event type, so each service gets only the events it handles.