support.* events

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_id is a team member's user id, an account with dashboard access, not the member's subscriber_id. The two are different namespaces.
  • Assignment is advisory. It does not restrict who may reply; anyone on the team with support-conversation:update still can.
  • Re-assigning to the same person fires the event again. Deduplicate on id if 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.
postWebhooksupport.conversation.assigned

Headers

SB-Signaturestring required

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=.

SB-Event-Idstring required

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.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'support.conversation.assigned' required

The event name, always support.conversation.assigned here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

Response

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.