Twilio conversations webhook events
Twilio sends 13 conversations events, including com.twilio.conversations.conversation.added, com.twilio.conversations.conversation.updated and com.twilio.conversations.conversation.removed. 12 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.conversations.conversation.added
documented from Twilio docs (example)
com.twilio.conversations.conversation.added Conversation is created
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.conversation.added",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ConversationAdded/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.conversation.added |
Full schema: 32 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.conversation.updated
documented from Twilio docs (example)
com.twilio.conversations.conversation.updated Conversation is updated
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.conversation.updated",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ConversationUpdated/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.conversation.updated |
Full schema: 15 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.conversation.removed
documented from Twilio docs (example)
com.twilio.conversations.conversation.removed Conversation is removed
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.conversation.removed",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ConversationRemoved/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.conversation.removed |
Full schema: 16 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.conversation-state.updated
documented from Twilio docs (example)
com.twilio.conversations.conversation-state.updated Conversation changes state
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.conversation-state.updated",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ConversationStateUpdated/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.conversation-state.updated |
Full schema: 14 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.message.added
documented from Twilio docs (example)
com.twilio.conversations.message.added Message is added to a conversation
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.message.added",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.MessageAdded/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.message.added |
Full schema: 24 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.message.updated
documented from Twilio docs (example)
com.twilio.conversations.message.updated Conversation message is updated
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.message.updated",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.MessageUpdated/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.message.updated |
Full schema: 23 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.message.removed
documented from Twilio docs (example)
com.twilio.conversations.message.removed Conversation message is removed
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.message.removed",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.MessageRemoved/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.message.removed |
Full schema: 24 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.participant.added
documented from Twilio docs (example)
com.twilio.conversations.participant.added Participant joins a conversation
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.participant.added",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ParticipantAdded/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.participant.added |
Full schema: 20 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.participant.updated
documented from Twilio docs (example)
com.twilio.conversations.participant.updated Conversation participant is updated
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.participant.updated",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ParticipantUpdated/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.participant.updated |
Full schema: 21 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.participant.removed
documented from Twilio docs (example)
com.twilio.conversations.participant.removed Participant leaves a conversation
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.participant.removed",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.ParticipantRemoved/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.participant.removed |
Full schema: 22 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.user.added
documented from Twilio docs (example)
com.twilio.conversations.user.added Conversations user is created
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.user.added",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.UserAdded/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.user.added |
Full schema: 13 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.user.updated
documented from Twilio docs (example)
com.twilio.conversations.user.updated Conversations user is updated
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
{
"specversion": "1.0",
"type": "com.twilio.conversations.user.updated",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/Conversations.UserUpdated/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.conversations.user.updated |
Full schema: 16 fields.
From Twilio docs
-
Content type
application/json
com.twilio.conversations.delivery.updated
documented No payload yet
com.twilio.conversations.delivery.updated Delivery receipt changes (discontinued by Twilio)
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource conversations
No payload yet.
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.