support.settings.updated

When this fires

A creator saves the project's support settings and at least one of the five visible settings is different afterwards:

Dashboard: Support Settings → Save from the support inbox.
REST: PATCH /v1/projects/{project}/support/settings. Fields you omit keep their stored value.
MCP: the update_support_settings tool.

It does not fire when:

Nothing changed. Saving the form untouched, or a PATCH that re-sends the stored values, writes nothing and emits nothing. Blank strings normalise to null before the comparison, so clearing an already-empty agent_name is not a change.
The bot links or unlinks the relay chat. That handshake changes the relay chat id, which is not one of the five settings this event covers.
A member's message is auto-acknowledged. Sending the auto_reply text is a message, not a settings change, and raises nothing in this family.

The relay chat id (the chat or forum group the bot forwards member messages to) is never in this payload. It is an identifier the bot's linking handshake writes, not a setting a creator types, and no surface can change it through this path.

Caveats

Subscribing needs support-conversation:view, but making the change needs the project update permission (project:update on a token), because the settings are columns on the project rather than on the inbox. A token that can read support threads can hear about settings changes it could not have made.
settings is always the full post-save state, even when only one key changed. You can overwrite a cached copy wholesale and use changes purely for "what to announce".
auto_reply is creator-authored template text and does appear in both settings and changes; it is the message members receive, not a message a member sent, so the family's rule about member text is intact.
Switching relay_mode to forum_group does not by itself link a group. The project bot links a group when the creator adds it to a supergroup with Topics enabled as an administrator, and confirms by DM; until that happens, notifications have nowhere to go and member messages reach only the dashboard inbox.

Related events

support.conversation.opened: the traffic these settings govern.
project.updated: other project-level edits, which never include the support columns.

Ability to subscribe

support-conversation:view

A token needs this to subscribe an endpoint to the event.

Header Parameters

SB-Signature*string

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-Id*string

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-Name*string

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

Content-Type*string

Always application/json.

User-Agent*string

Always Subscriby-Webhooks/1.0.

Payload

JSONWhat Subscriby posts to your endpointapplication/json

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

id*string

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

type*"support.settings.updated"

The event name, always support.settings.updated here.

Value in

"support.settings.updated"

created_at*string

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

Formatdate-time

api_version*string

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

project_id*|

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

Formatuuid

data*

The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.

Responses

2XXAny success status

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

defaultAny other status

Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.

Delivery to your endpoint

Subscriby sends this event as one HTTP request to every endpoint subscribed to it.

POSThttps://example.com/webhooks/subscribyyour endpoint URL

Headers

SB-Signature: t=1758636300,v1=5f1c…
SB-Event-Id: 01HXDELIVERY000000000TST
SB-Event-Name: support.settings.updated
Content-Type: application/json
User-Agent: Subscriby-Webhooks/1.0

Body

{  "id": "evt_01HX...",  "type": "support.settings.updated",  "created_at": "2026-09-06T10:02:00Z",  "api_version": "2026-05-01",  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",  "data": {    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "settings": {      "enabled": true,      "relay_mode": "owner_dm",      "agent_name": "Team Research Premium",      "auto_reply": null,      "notify_email": false    },    "changes": {      "relay_mode": {        "from": "none",        "to": "owner_dm"      },      "agent_name": {        "from": null,        "to": "Team Research Premium"      }    }  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Body {  id: string;  type: "support.settings.updated";  created_at: string;  api_version: string;  project_id: string | null;  data: Data;}export interface Data {  project_id: string;  settings: Settings;  changes: Changes;}export interface Settings {  enabled: boolean;  relay_mode: "none" | "owner_dm" | "forum_group";  agent_name: string | null;  auto_reply: string | null;  notify_email: boolean;}export interface Changes {  enabled?: Enabled;  relay_mode?: RelayMode;  agent_name?: AgentName;  auto_reply?: AutoReply;  notify_email?: NotifyEmail;}export interface Enabled {  from: boolean;  to: boolean;}export interface RelayMode {  from: "none" | "owner_dm" | "forum_group";  to: "none" | "owner_dm" | "forum_group";}export interface AgentName {  from: string | null;  to: string | null;}export interface AutoReply {  from: string | null;  to: string | null;}export interface NotifyEmail {  from: boolean;  to: boolean;}

When it arrives

Verify the signatureCheck the SB-Signature header before trusting anything in the body.Answer 2xx within 30 secondsAny other answer, or none, and Subscriby retries the delivery.

De-duplicate on SB-Event-IdA retry carries the same id as the first attempt.