Skip to main content
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.
  3. Then open Connection.

​
Connect an account

1

Select the toolkit

Find Slack, Google, Telegram, or the toolkit you need. Use search if the list is long.
2

Start connect

Choose Connect (or equivalent). Complete the provider’s consent screen. Flowra uses standard OAuth; review the scopes before approving.
3

Confirm status

Return to Connection and confirm the row shows an active status.
4

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, replies use the account you attach there.

​
Status labels

You can set a Display name (dashboard-only label, for example Work Gmail) without changing the provider account.

​
Tips

  • Multiple connections per toolkit may exist — pick the right default inside the workflow.
  • OAuth toolkits often need App credentials on the project before Connect works.
  • After cloning a 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.

​
Developers

Programmatic link flow and list/delete: Connected accounts and Auth configs. Product UI for credentials: App credentials.