> 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 three-pane connector detail view and its five tabs.

`/integrations/connectors/<slug>`. Three panes: the connector list on the left, that connector's actions in the middle, and the detail tabs on the right.

* **Left**: **Back to all connectors**, **Create a connector**, a search box, and the connector list with `<Name> operations` expanders. Connectors your org owns also get **Add action**.
* **Middle** (the action list, each with a method chip (`GET`, `POST`, `PUT`, `PATCH`, `DELETE`), plus **Select all**. Selecting actions is how you scope what a workflow or an agent may use), the point of *read-only Jira for one customer, nothing beyond that*.
* **Right**: the connector name, a `<owner> · <auth type>` line, a version chip such as `v1.0 · Test`, a **Connect** button, and a `⋯` menu with **Edit** and **Delete**. Below that, five tabs.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-e030cf5537d1d4d99b2af0087f1158782e9d74a0%2Fconnector-detail-overview.jpg?alt=media" alt="The HubSpot connector&#x27;s Overview tab: tiles reading 0 Connections, 1 Auth method and v1.0 Current version, over a Details table giving slug hubspot, Visibility Public and Created Aug 20, 2026"><figcaption><p>The version tile reads <em>In test, not published</em>, the connector works, but no customer can reach it yet.</p></figcaption></figure>

#### Overview

Three tiles (**Connections**, **Auth method(s)**, **Current version**) and a details table.

| Field            | Meaning                                                                                          |
| ---------------- | ------------------------------------------------------------------------------------------------ |
| **Slug**         | The identifier used in API paths and in workflow code.                                           |
| **Visibility**   | Private or Public. New connectors start Private; publishing publicly is a platform-admin action. |
| **Auth methods** | What your customers authorise with.                                                              |
| **Created**      | When it entered the catalogue.                                                                   |

A **Versions** section underneath carries a `Test` / `Live` toggle and a **Publish to live** control.

#### Auth

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-62f77dd450962c629543cdb18f65dbaf99277366%2Fconnector-auth-tab.jpg?alt=media" alt="The HubSpot connector&#x27;s Auth tab, headed Authentication methods, with a single row: OAuth 2.0 badged Default, 1 provider, and a View providers button top-right"><figcaption><p>The providers link opens the OAuth apps sitting behind that method.</p></figcaption></figure>

One row per authentication method, each showing its provider count, plus a **View providers** button that opens the OAuth apps behind them. The tab describes each shape in your customer's terms:

> Your customers sign in with the provider and approve access.

> Your customers paste a key they generate themselves.

#### Connections

Every customer who has authorised this connector. Before anyone has, it reads `Nobody has connected yet`. It is the same data as the workspace-wide [Connections](/build/connections.md) page, filtered to this one system.

#### Version pins

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

That second sentence is the rule that matters: a pin is a fallback, not an override. Pin a customer when they cannot absorb a change yet (a field they depend on moved, or their own integration needs a release first), then unpin them when they are ready.

With nothing to pin, the tab reads `No versioned actions yet` / *Add actions with an externalVersion to enable per-tenant routing.*

The tab also carries a **Compare two versions** tool: `Action slug`, `From`, `To`, `From major`, `To major`, and **Compare**.

#### Webhook config

**New config** creates one. Until then:

> No webhook config yet

> Until one exists, customers of this connector can be polled but cannot be notified.

That is the plumbing behind an [app event trigger](/build/triggers.md): configure it once here and app event triggers on this connector work for every customer, rather than each of them registering a webhook themselves.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.