connector.* events

The creator connected an installation with their credentials; the connector can act for the project now.

When this fires

A creator completes a connector's connect flow on the dashboard: the connector checks the credentials, registers with its platform and the installation turns connected. For the first connector this is the Connect Bot modal, the platform bot's connectivity conversation and a Disaster Recovery bot replacement.

Caveats

  • Credentials are never in the payload. Read the installation back with the installation endpoint.
  • Reconnecting with new credentials fires this again for the same installation_id.

Related events

  • connector.installed: the pending row that preceded it, when the connector installs in two steps.
  • connector.status_changed: the installation's health afterwards.
postWebhookconnector.connected

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'connector.connected' required

The event name, always connector.connected 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.