support.* events

A support conversation is marked resolved and leaves the open queue.

When this fires

A conversation is marked resolved from the dashboard inbox, the REST API, Zapier, n8n, or the resolve_support_conversation MCP tool.

Resolving is not closing. The thread and its full history are kept, and it reopens by itself the moment the member writes again, which raises support.conversation.reopened.

Caveats

  • Resolving does not notify the member. If you want them to know the matter is closed, send a reply before resolving.
  • The event fires even if the conversation was already resolved. Deduplicate on id.
  • A resolved conversation still counts toward the member's history and still appears under the Resolved tab in the inbox; it is filtered out of the open queue, not deleted.

Related events

  • support.conversation.reopened: what happens when the member writes back.
  • support.message.sent: the reply that usually precedes resolving.
postWebhooksupport.conversation.resolved

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.resolved' required

The event name, always support.conversation.resolved 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.