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

# Connections

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

***

## Connection Card

Each card on the Connections page 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

***

## Connection Statuses

| Status | What it means                                                                                |
| :----- | :------------------------------------------------------------------------------------------- |
|        | Active and authenticated. Integrations using this connection will run normally.              |
|        | Authentication has not been completed or has expired. Integrations will fail until resolved. |

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

***

## Authentication Types

<CardGroup cols={2}>
  <Card title="OAuth2" icon="key">
    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.
  </Card>

  <Card title="Custom" icon="terminal">
    Used by apps that don't support OAuth2 — like Visma e-conomic. Typically involves entering an API key or credentials directly.
  </Card>
</CardGroup>

***

## Adding a New Connection

Click **+ Add New** in the top right corner.

<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 own login page to authorize access. For **Custom** apps, you'll enter your API key or credentials directly.
  </Step>

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

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

***

## Managing a Connection

Click the **three-dot menu** on any connection card.

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

  <Card title="Delete" icon="trash">
    Permanently removes the connection. Any integration depending on it will stop working. Only delete 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. Re-authorize the affected connection — 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 — useful when you have separate production and staging accounts, multiple HubSpot portals or QuickBooks companies, or different credentials for different teams.

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="table-list" href="/workflow-runs">
    If a run failed due to a connection issue, re-trigger it here after re-authorizing.
  </Card>

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