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

# Connections

> Link third-party accounts (OAuth) so tools and workflows can act on behalf of the selected end user.

The **Connection** screen manages OAuth (and similar) links grouped by toolkit. Without a healthy connection, tools that need login fail with auth errors.

Connections belong to the **active external user** (the sidebar **End user** switcher), not only to the project. If you connect Slack while “Default user” is selected, that Slack link is for the default user — not for `customer_alice`.

## Before you connect

1. Select the correct **project**.
2. Select the correct **end user** — see [External users switcher](/product/external-users).
3. Then open [Connection](https://flowra.dev/dashboard/connection).

## Connect an account

<Steps>
  <Step title="Select the toolkit">
    Find Slack, Google, Telegram, or the toolkit you need. Use search if the list is long.
  </Step>

  <Step title="Start connect">
    Choose **Connect** (or equivalent). Complete the provider’s consent screen. Flowra uses standard OAuth; review the scopes before approving.
  </Step>

  <Step title="Confirm status">
    Return to Connection and confirm the row shows an active status.
  </Step>

  <Step title="Bind it to a workflow">
    In the workflow editor, set which connected account is the default for that toolkit when the UI offers account binding. For messaging [entry points](/product/entry-points-and-channels), replies use the account you attach there.
  </Step>
</Steps>

## Tips

* Multiple connections per toolkit may exist — pick the right default inside the workflow.
* After cloning a [Marketplace](/product/marketplace) template, reconnect accounts; templates do not bring your OAuth tokens.
* Channel and widget visitors get their own external users automatically; connect (or re-authorize) under that user when debugging their tools.
* For SaaS backends, create a stable username and send the same value as `x-username`. See [Multi-tenancy](/guides/multi-tenancy).

## Developers

Programmatic link flow and list/delete: [Connected accounts](/guides/connected-accounts) and [Auth configs](/guides/auth-configs).