connector.settings_updated

A declared setting of an installation changed — which fields, never their values.

When this fires

A creator changes an installation's settings, on the dashboard, through PATCH …/installation/settings or the update_connector_installation_settings tool, and at least one declared field took a new value. A write that changes nothing fires nothing.

Required ability

project-connector:view — token must carry this at mint time to subscribe an endpoint to this event.

Payload

{
  "id": "evt_01HX...",
  "type": "connector.settings_updated",
  "created_at": "2026-09-12T10:20:00Z",
  "api_version": "2026-05-01",
  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
  "data": {
    "connector": "discord",
    "installation_id": "3b8f0c6e-2d41-4a97-9e5f-1c7d6b2a8e40",
    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
    "changed_fields": ["greeting"]
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `connector.settings_updated` for this event.
`created_at`	ISO 8601 timestamp	Server-side emission time.
`api_version`	string	Webhook API contract version.
`project_id`	string UUID	Project this event belongs to.
`data.connector`	string	The connector key.
`data.installation_id`	string UUID	The installation row.
`data.project_id`	string UUID	Mirrors top-level `project_id`.
`data.changed_fields`	string[]	The declared field names that took a new value, as the connector's `settings_fields` name them, and `capabilities.<key>` for each capability switch that changed.

Caveats

Values are never in the payload, and the installation endpoints never serialise settings either, because a settings field may be a secret. A consumer that needs the value asks the creator.

connector.connected — the installation the settings belong to.
Connector events overview — back to family overview.