---
title: "A connector was installed on a project: a pending installation with no credentials yet."
method: POST
path: "connector.installed"
tags: ["connector.* events"]
---

# A connector was installed on a project: a pending installation with no credentials yet.

`POST connector.installed` (webhook)

### When this fires

A creator (or a token) installs a connector on a project: from the Connectors tab, through [the install endpoint](https://docs.subscriby.net/api/v1/reference/connectors) or the [`install_connector`](https://docs.subscriby.net/mcp/v1/tools/connectors/install-connector) tool. Installing says "this project runs this connector" and opens the row the Connectors tab shows as **pending**; connecting, which hands the connector the creator's credentials, is a separate act and fires `connector.connected`. Installing a connector that is already installed changes nothing and fires nothing; bringing an uninstalled connector back fires this again, the row pending once more with its settings kept.

### Caveats

- A second distinct connector on a project needs the owner's `multi_connector` capability (Growth); the install is refused `CONNECTOR_TIER_REQUIRED` and nothing fires.
- The first connector's bot flow connects in one step from the dashboard, so an existing project sees `connector.connected` without a preceding `connector.installed`.

### Related events

- `connector.connected`: the credentials handed over.
- `connector.disconnected`: the reverse.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, 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.installed', required: The event name, always `connector.installed` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `connector` string, required: The connector key, as the [directory](https://docs.subscriby.net/api/v1/reference/connectors) lists it.
    - `installation_id` string, uuid, required: The installation row; what the project's connector endpoints return as `id`.
    - `project_id` string, uuid, required: Mirrors top-level `project_id`.
    - `state` string, required: Always `pending` here: nothing is connected yet.

## Acknowledgement `2XX`

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

## Other responses

- `default`: 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.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)