> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/connectors/inside-a-connector.md).

# Inside a connector

The connector detail page: the connector rail, the header, and the Overview, Connections and Version pins tabs.

`/integrations/connectors/<slug>`. Click a connector's name in the catalogue to open it.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-fd6ff5069cc6c6a5067977a2b4a939fc3271494f%2Fconnector-detail-overview.webp?alt=media" alt="The HubSpot connector detail page: on the left the connector rail with HubSpot expanded to its 162 actions, each with a method chip such as PUT or DELETE and a checkbox; on the right the header HubSpot, Fastn · OAuth 2.0, a v1.0 · Test chip, a Disconnect button and a three-dot menu, the tabs Overview, Auth, Connections, Version pins and Webhook config, and the Overview tab with tiles 1 Connection, 1 Auth method and v1.0 Current version above a Details table"><figcaption><p>The detail page has two panes: the connector rail on the left and the selected connector on the right.</p></figcaption></figure>

### The connector rail (left)

* **←** (Back to all connectors) returns to the catalogue.
* **+** (Create a connector) opens the [Create a connector](/build/connectors/creating-a-connector.md) dialog.
* **Search connectors** filters the rail.
* Every connector is listed with its icon. The open connector is expanded: it shows its action count, a green dot if it is connected, and a chevron that collapses or expands its action list.
* Under it, **Select all** and one row per action, each with a checkbox and a method chip (`GET`, `POST`, `PUT`, `PATCH`, `DELETE`). Click an action to open it in the [action editor](/build/connectors/action-detail.md). Tick actions to export them; see [Importing and exporting](/build/connectors/importing-and-exporting.md).

### The header

| Element                                 | Meaning                                                                                                                                                                                                      |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name** and icon                       | The connector.                                                                                                                                                                                               |
| `<owner> · <auth type>`                 | Who maintains it (*Fastn* for managed connectors, your organisation's name for connectors you own) and its default auth type, for example `Fastn · OAuth 2.0` or `Fastn · INPUT`.                            |
| Version chip, for example `v1.0 · Test` | The connector's current version and whether that version is in **Test** or **Live**.                                                                                                                         |
| **Connect** or **Disconnect**           | **Connect** opens the connect dialog. Once you are connected it changes to **Disconnect**, which removes your connection after a confirmation.                                                               |
| **⋯** (More actions)                    | On a managed connector you are connected to: **Disconnect**. On a connector your workspace owns: **Edit** and **Delete**; see [Editing, publishing and deleting](/build/connectors/editing-and-deleting.md). |

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-757435f26b761d8438b266a16a61df93556b017a%2Fconnector-detail-menu.webp?alt=media" alt="The HubSpot header with the three-dot menu open, showing one item, Disconnect"><figcaption><p>On a managed connector the menu only offers <strong>Disconnect</strong>.</p></figcaption></figure>

Below the header are five tabs: **Overview**, **Auth**, **Connections**, **Version pins** and **Webhook config**. **Auth** is covered in [Auth methods and providers](/build/connectors/auth-methods.md) and **Webhook config** in [Webhook config](/build/connectors/webhook-config.md).

### Overview

The connector's description, then three tiles:

| Tile                | Shows                                                                                               |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| **Connection(s)**   | How many connections use this connector (*Customers using this connector*).                         |
| **Auth method(s)**  | How many auth methods it offers, and which is the default, for example *OAuth 2.0, set as default*. |
| **Current version** | The current version, and *In test, not published* or the live state.                                |

Then a **Details** table:

| Field            | Meaning                                                                                                                                                                   |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Slug**         | *Used in the API path and in code.*                                                                                                                                       |
| **Visibility**   | **Private**: only your workspace can see it. **Public**: *Workspaces under your organization can use it when Catalog connectors is on. Other organizations never see it.* |
| **Auth methods** | *What your customers authorise with.*                                                                                                                                     |
| **Created**      | When the connector was added.                                                                                                                                             |

#### Versions

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-fd6ff5069cc6c6a5067977a2b4a939fc3271494f%2Fconnector-detail-overview.webp?alt=media" alt="The HubSpot Overview tab with the Details table and, below it, a Versions section with a Test/Live toggle listing v1.1 Test, Auto-versioned on update, Jun 2, 2026, and v1.0 Test, Initial version, Jun 2, 2026"><figcaption><p>The Versions list with the <strong>Test</strong> toggle selected.</p></figcaption></figure>

Every saved change to a connector creates a version. The **Versions** section lists them, newest first, with a note such as *Initial version* or *Auto-versioned on update* and the date.

* **Test** lists versions that are still being tested. Customers do not run them.
* **Live** lists published versions, the ones customers run.

If a list is empty it reads *No test versions yet.* (or the live equivalent). On a connector your workspace owns, each test version also has a **Publish to live** button; see [Editing, publishing and deleting](/build/connectors/editing-and-deleting.md#publish-a-version).

### Connections

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-156249c8809da380c86067bea2b6a8f903c29698%2Fconnector-tab-connections.webp?alt=media" alt="The HubSpot Connections tab: a Connect button top right and a table with columns Name, Status and Default, holding one row named default with a blurred connection ID, status Active, a Default badge and a delete icon"><figcaption><p>Every connection made on this connector. The second line of each row is the connection ID (blurred here).</p></figcaption></figure>

> Every customer who has authorised this connector. Make one yourself to test the flow end to end.

| Column      | Meaning                                                                                      |
| ----------- | -------------------------------------------------------------------------------------------- |
| **Name**    | The connection's name (`default` unless it was named), with its connection ID underneath.    |
| **Status**  | `Active`, `Inactive`, `Expired` or `Failed`. See [Statuses](/build/connections/statuses.md). |
| **Default** | Marks the connection that is set as the default for this connector.                          |
| 🗑          | Disconnects that connection.                                                                 |

**Connect** adds a connection. Before anyone has connected, the tab reads *Nobody has connected yet* with a **Connect \<connector>** button:

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-6a86a6fb9454bf35d61be4969b66e3058d8f7a31%2Fconnector-tab-connections-empty.webp?alt=media" alt="The AbstractAPI Holidays Connections tab reading Nobody has connected yet, A connection appears here once one of your customers authorises AbstractAPI Holidays, with a Connect AbstractAPI Holidays button"><figcaption><p>The empty state on a connector nobody has connected yet.</p></figcaption></figure>

This tab shows the same connections as the workspace-wide [Connections](/build/connections.md) page, limited to one connector.

### Version pins

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-2dda77028125c95ee879c7eb2b35701e39af4840%2Fconnector-tab-version-pins.webp?alt=media" alt="The HubSpot Version pins tab: an empty state reading No versioned actions yet, Add actions with an externalVersion to enable per-tenant routing, and below it a Compare two versions panel with Action slug, From, To, From major and To major fields and a Compare button"><figcaption><p>Version pins and the version comparison tool.</p></figcaption></figure>

> Hold one customer on one version while everyone else moves on. A version set in code still wins over a pin.

A pin keeps one customer on an older version of an action while every other customer moves to the new one. Use it when a customer cannot take a change yet, for example because a field they depend on moved. Remove the pin when they are ready.

The second sentence matters: a pin is a fallback. If a workflow asks for a specific version in its code, that version is used, pin or not.

Pins work on actions that have an external version (`externalVersion`), which you create in the action editor with **New version → New external version** (see [Actions](/build/connectors/action-detail.md#versions)). Until a connector has such actions, the tab reads *No versioned actions yet* · *Add actions with an externalVersion to enable per-tenant routing.*

**Compare two versions** shows what changed in an action's contract between two versions before you upgrade or deprecate:

| Field                         | What to enter                                                              |
| ----------------------------- | -------------------------------------------------------------------------- |
| **Action slug**               | The action to compare, for example `createOrder`.                          |
| **From** / **To**             | The two provider versions.                                                 |
| **From major** / **To major** | The internal major versions (`Default` or `major 1`, `major 2` and so on). |

**Compare** shows the difference.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/build/connectors/inside-a-connector.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.