ProviderOutboundMessage event fires when a user sends a message to a contact and a custom external communication provider is configured as the default channel for the sub-account. This event differs from the standard OutboundMessage event — the payload is smaller and structured specifically for provider routing rather than conversation tracking. Only the fields listed below will be present.
Supported channels
| Channel | Supported modules |
|---|---|
| SMS | Web App, Mobile App, Workflows, Bulk Actions |
| Web App, Mobile App, Workflows, Bulk Actions |
Payload
| Field | Type | Description |
|---|---|---|
type | string | Channel type for this message. Either "SMS" or "Email" |
locationId | string | Sub-account ID from which the message was sent |
messageId | string | Unique identifier for the message |
contactId | string | ID of the contact who received the message |
userId | string | ID of the user who sent the message |
attachments | array | List of attachment URLs; empty array if none |
message | string | Text body of the message (SMS only) |
phone | string | Recipient phone number in E.164 format (SMS only) |
emailMessageId | string | Provider-assigned message ID for email (Email only) |
emailTo | string | Recipient email address or addresses (Email only) |
emailFrom | string | Sender display name and email address, e.g. From Name <email@example.com> (Email only) |
html | string | Full HTML body of the email (Email only) |
subject | string | Email subject line (Email only) |
Example payload
SMS
Related
- Outbound Message — fires for standard outbound messages not routed through a custom provider
- Inbound Message — fires when a contact sends a message to a user
- Conversations API — query conversations and messages programmatically
.png?fit=max&auto=format&n=EQK5eX9kTD8NzWwA&q=85&s=878008bf159fcc4964d0c0d508b6e400)