connector.uninstalled
A connector was uninstalled from a project: its grants revoked, its resources detached, the installation row kept, with the counts of what that touched.
When this fires
A creator uninstalls a connector from a project, from the Connectors tab, through the uninstall endpoint or the uninstall_connector tool, after the impact preview. Uninstalling is distinct from disconnecting and never a deletion: every live grant on the connector's resources is revoked (member.resource_removed fires per grant), the resources are deactivated as detached with their external ids kept, the installation row stays with uninstalled_at, identities are never removed and no money moves by itself. The two opt-ins act on the plans left with nothing to grant: taking them off sale fires plan.deactivated per plan, cancelling their recurring subscriptions at period end fires subscription.cancelled per subscription.
Caveats
- Members are told by email that their recurring subscription will not renew; nothing is taken from them before the end of the paid period.
- Installing the connector again brings the same installation back as pending with its settings kept; the detached resources stay inactive until the creator relinks them.
Related events
connector.disconnected: the reversible act this is not.connector.installed: the reinstall.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
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.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
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.
How is this guide?
Last updated on