support.conversation.assigned
A support conversation is handed to a team member, or its assignment cleared.
When this fires
A conversation's assignee changes: it is handed to a team member from the dashboard inbox, the REST API, Zapier, or n8n, or an existing assignment is cleared.
Clearing an assignment fires this same event with
data.assigned_to_user_id: null. There is no separate "unassigned" event; branch on the null.
Caveats
assigned_to_user_idis a team member's user id, an account with dashboard access, not the member'ssubscriber_id. The two are different namespaces.- Assignment is advisory. It does not restrict who may reply; anyone on the team with
support-conversation:updatestill can. - Re-assigning to the same person fires the event again. Deduplicate on
idif you are posting notifications.
Related events
support.conversation.resolved: the usual next step once the assignee has answered.support.message.received: what typically prompts an assignment.
Header Parameters
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Request Body
application/json
The signed JSON envelope posted to your endpoint.
TypeScript Definitions
Use the request body type in TypeScript.
The envelope every event is delivered in.
Response Body
Example Requests
/support.conversation.assignedHow is this guide?