Conversation Message

Trigger workflow when a customer sends a new message on a Zendesk messaging channel (Sunshine Conversations).

trigger/conversation-message — Trigger workflow when a customer sends a new message on a Zendesk messaging channel (Sunshine Conversations).

Where it appears

The Conversation Message block is a trigger — it starts a workflow. Add it from the Triggers group in the Workflow Builder.

Field	Type	Required	Default	Description
`channels`	multi-select	No	—	Limit to specific messaging channels. Leave all unchecked to fire on any channel. Options: `whatsapp`, `messenger`, `instagram`, `web`, `ios`, `android`, `twitter`, `line`, `viber`, `telegram`, `wechat`, `kakao`, `sms`, `googlebusinessmessages`, `applebusinesschat`.
`brandIds`	list	No	—	Limit to conversations on specific Zendesk brands. Leave empty to fire on any brand.
`firstMessageOnly`	toggle	No	`false`	Fire only on the first inbound message on a conversation (e.g. for auto-greet workflows).
`testInput`	code	No	—	Sample message-event JSON to use when running this workflow in test mode instead of waiting for a real inbound conversation message.

Inputs are the configurable fields above. The block produces these outputs:

Outputs

Reference an output downstream with <Conversation Message.field>.

Name	Type	Description
`triggered`	boolean	Whether the trigger fired
`timestamp`	number	Trigger timestamp (epoch ms)
`conversationId`	string	Sunshine Conversations conversation ID
`ticketId`	string	Zendesk ticket ID resolved from the conversation
`messageId`	string	SC message ID
`messageText`	string	Message text body
`messageTimestamp`	string	ISO 8601 timestamp of the message
`authorUserId`	string	SC user ID of the message author
`channel`	string	SC channel type (e.g. whatsapp, web, messenger)
`brandId`	string	Zendesk brand ID, if available
`subdomain`	string	Zendesk subdomain
`webhookEventId`	string	Deduplication ID for the originating webhook event

A minimal configuration for this block:

{
  "type": "trigger/conversation-message",
  "config": {
    "firstMessageOnly": false
  }
}