> 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/connections.md).

# Connections

Authenticated links between your customers and their systems.

**Integrations → Connections** · `/integrations?tab=connections`

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-9c21781fd833d67775c6561d3562f1d36aebf740%2Fconnections-list.jpg?alt=media" alt="The Connections table, 5 connections, under Connector, Customer, Auth, Status and Created: TikTok Shop on OAUTH, Cin7 Core and three unnamed connector IDs on INPUT, every row Active with an em dash for Customer"><figcaption><p>The Auth column shows the raw internal values, <code>OAUTH</code> and <code>INPUT</code> here. A connector with no catalogue entry shows its raw ID instead of a name.</p></figcaption></figure>

A connection is one customer's authorised link to one connector. It holds the credential (encrypted, never displayed) and records how it was obtained.

### How connections work

A connection is an authenticated link between one of your customers and one connector: the stored, encrypted result of that customer authorising access once, which every later API call reuses so nobody signs in again. A few properties are worth holding in mind before the detail below:

* **Who it belongs to: Scope.** Most connections belong to a single customer (one tenant). Some belong to your organisation instead: those read `Account level` on the detail page, meaning the link is shared across the workspace rather than tied to one customer.
* **How you address it: the connection ID.** Every connection has an id of the form `ucl:org_<org>:<env>:<connectorId>:<authId>:<tenant>`. You pass it to the API to act as that customer, and it is what routes a call to the right credential.
* **Whether it still works: Status.** A connection is `Active`, `Inactive`, `Expired` or `Failed`. Active needs nothing; the other three need attention.
* **Fixing or ending one: Reconnect / Disconnect.** Every row's `⋯` menu offers **Reconnect** (re-run authorisation to restore a broken link) and **Disconnect** (syncing stops and the credential is deleted).
* **Making one yourself: the picker.** **New connection** opens the full-screen **Connect a system** picker; customer connections should instead come through your embedded widget.

The rest of this page is the detail behind each of those.

### The table

| Column        | What it tells you                                   |
| ------------- | --------------------------------------------------- |
| **Connector** | The system, with the tenant key on the second line. |
| **Customer**  | Which customer owns it.                             |
| **Auth**      | How it was authorised.                              |
| **Status**    | Active, Inactive, Expired or Failed.                |
| **Created**   | When the customer authorised it.                    |
| **⋯**         | **Reconnect** and **Disconnect**.                   |

The table pages at 10 rows. Filter chips above it (**All**, **Active**, **Inactive**, **Expired**, **Failed**), are not kept in the URL, so a filtered view cannot be linked.

{% hint style="warning" %}
The `Active`, `Inactive`, `Expired` and `Failed` chips currently return nothing, even when every row in the unfiltered table shows `Active`. Until that is fixed, triage from the full list rather than the chips.
{% endhint %}

### In this section

* [Statuses](/build/connections/statuses.md)
* [Auth types](/build/connections/auth-types.md)
* [Inside a connection](/build/connections/inside-a-connection.md)
* [Creating a connection](/build/connections/creating-a-connection.md)


---

# 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/connections.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.