> 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/connect-a-system.md).

# Connect a system

Making a connection step by step: open the connect dialog, choose the auth method, give the credential, and check that it worked.

A connection is what lets a connector call an app as a specific account. Connecting here signs in **your own** account, for your organisation's workflows and for testing. Your customers connect their own accounts through the [widget](/embed/embed.md) you embed.

These all open the same connect dialog:

* **Connect** on a connector's card in the [catalogue](/build/connectors/the-catalogue.md);
* **Add another connection** on a card that is already connected;
* **Connect** in the header, or on the **Connections** tab, of the [connector detail page](/build/connectors/inside-a-connector.md);
* **New connection** on the [Connections](/build/connections.md) page, then pick the app.
* **⋯ → Connect** on the connector's row in the rail, for a connector your workspace owns.

{% stepper %}
{% step %}

#### Open the connect dialog

Use any of the entry points above. The dialog is titled **Connect \<app>**, with the chosen auth method shown next to the name.
{% endstep %}

{% step %}

#### Choose the auth method

If the connector offers more than one method, an **Auth Method** selector appears. It starts on the connector's default method. Pick another if you need to, for example a personal access token instead of OAuth.
{% endstep %}

{% step %}

#### Give the credential

What the dialog asks for depends on the method.

**API key, bearer token and other keyed methods**: the dialog shows one field per credential, for example **API Key**. Paste the value and click **Connect**.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-9f3f528ac863c8e61b4d2aeb3a3e5c5589f687c2%2Fconnections-connect-apikey.webp?alt=media" alt="The Connect AbstractAPI Holidays dialog, tagged API Key, with a single API Key field and the note Stored encrypted and scoped to this workspace, with Cancel and Connect buttons"><figcaption><p>An API key method needs one field.</p></figcaption></figure>

**OAuth 2.0**: the dialog shows *You will authorise in a new window*, the **Auth provider** it will use, and **Scopes**. Click **Authorise**, sign in to the app in the new window and approve access.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-28a382f818dc852875bc53cbd1a62e3866a16470%2Fconnectors-connect-oauth.webp?alt=media" alt="The Connect Asana dialog: You will authorise in a new window, an Auth Method selector set to Connect with Asana OAuth, the Auth provider Asana OAuth marked Default with a blurred client ID, a Scopes selector reading All scopes (default), and Cancel and Authorise buttons"><figcaption><p>An OAuth method. Nothing is stored until you come back from the app.</p></figcaption></figure>

The scope and provider options are explained in [Creating a connection](/build/connections/creating-a-connection.md#connecting-with-oauth).
{% endstep %}

{% step %}

#### Check that it worked

The card's badge changes to **Connected** and its button to **Add another connection**. The connection appears on the connector's **Connections** tab and on the [Connections](/build/connections.md) page with the status `Active`.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Every credential is *Stored encrypted and scoped to this workspace. Your customers never see it, and you can revoke it at any time.* To revoke it, disconnect the connection; see [Inside a connection](/build/connections/inside-a-connection.md).
{% endhint %}


---

# 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/connect-a-system.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.