> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fourgent.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connections

> Manage the app credentials that power your integrations.

Connections are the authenticated links between Fourgent and your apps. Every integration depends on at least two connections — one for the source app and one for the destination. If a connection breaks, the integrations that depend on it will fail.

This page is where you add, monitor, and fix your connections.

***

## The Connections Page

Each card represents a named connection to an app. The card shows:

* **Connection name** — the label you gave it when setting it up
* **Connection ID** — Fourgent's internal ID (useful when contacting support)
* **Status** — whether the connection is active
* **App and auth type** — the app being connected and the method used (OAuth2 or Custom)

***

## Connection Statuses

| Status            | What it means                                                                                                           |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Connected**     | The connection is active and authenticated. Integrations using this connection will run normally.                       |
| **Not Connected** | Authentication has not been completed or has expired. Integrations using this connection will fail until it's resolved. |

<Warning>
  A **Not Connected** status means any integration that depends on this connection will fail when it fires. Re-authorize the connection as soon as possible to restore normal operation.
</Warning>

***

## Authentication Types

Fourgent supports two authentication methods depending on what the app requires.

| Type       | What it means                                                                                                                                               |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **OAuth2** | The standard for apps like HubSpot, QuickBooks, and Slack. You authorize Fourgent through the app's own login flow — no API keys to copy or store manually. |
| **Custom** | Used by apps that don't support OAuth2 — like Visma e-conomic. Typically involves entering an API key or other credentials directly.                        |

***

## Adding a New Connection

Click **+ Add New** in the top right. Fourgent will prompt you to select the app and walk you through the authentication flow.

<Steps>
  <Step title="Select the app">
    Choose the app you want to connect from the list of supported connectors.
  </Step>

  <Step title="Authenticate">
    For **OAuth2** apps, you'll be redirected to the app's login page to authorize access. For **Custom** apps, you'll enter your API key or credentials directly.
  </Step>

  <Step title="Name the connection">
    Give the connection a descriptive name — especially useful if you have multiple accounts for the same app (e.g. a staging and production HubSpot account).
  </Step>

  <Step title="Confirm">
    Once authenticated, the connection card will appear with a **Connected** status and its assigned ID.
  </Step>
</Steps>

***

## Managing an Existing Connection

Click the **three-dot menu** on any connection card to see the available actions.

<CardGroup cols={2}>
  <Card title="Re-authorize" icon="rotate">
    Refreshes the authentication. Use this when a connection shows **Not Connected**, or when you've rotated API keys or changed account credentials in the source app. The connection ID stays the same — your integrations are not affected.
  </Card>

  <Card title="Delete" icon="trash">
    Permanently removes the connection. Any integration that depends on this connection will stop working. Only delete a connection if you're sure no active workflows are using it.
  </Card>
</CardGroup>

<Tip>
  If a workflow run fails with an authentication error, come here first. Find the connection for that app and re-authorize it — then re-trigger the failed run from **Workflow Runs**.
</Tip>

***

## Multiple Accounts for the Same App

You can create more than one connection for the same app. This is useful when you have:

* Separate production and staging accounts
* Multiple HubSpot portals or QuickBooks companies
* Different API credentials for different teams or workflows

Each connection gets its own card and ID. When building an integration, Fourgent will ask which connection to use if more than one exists for the same app.

***

## Related

<CardGroup cols={2}>
  <Card title="Workflow Runs" icon="list-check" href="/workflow-runs">
    If a run failed due to a connection issue, re-trigger it here after re-authorizing.
  </Card>

  <Card title="Supported Connectors" icon="plug" href="/connectors">
    Browse every app Fourgent can connect to out of the box.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/workflows">
    See which integrations are using your connections.
  </Card>

  <Card title="Settings" icon="gear" href="/settings">
    Manage workspace-level settings and billing.
  </Card>
</CardGroup>