Connecting apps

Super Flows acts in your other apps through connections. An owner or admin connects an app once, on the Apps page, and every workflow and agent in the organization uses it. Every run acts with those connections, whoever or whatever started it.

Connections go through Super Connect, which holds the sign-in and keeps it fresh. The apps on offer come from its catalog, and the list grows over time.

What a connection is

A connection is one account of one app. It belongs to the organization, not to the person who connected it. Two accounts of the same app are two connections, and each Google app is its own connection: connecting Gmail does not connect Google Sheets.

Action steps act as a connection’s account. Agents act only through the connections they are granted. See Grants and approvals.

Who can connect

Only owners and admins connect, reauthorize and disconnect apps. Members see the Apps page and every connection on it, without those buttons. Where a member would connect an app, the builder and the agent editor say Ask an admin. See Roles.

Connect an app

1. Open the Apps page.
2. Press Connect an app.
3. Choose the app in the Super Connect window.
4. Sign in to the app and approve the access it asks for.
5. Finish when the window reaches Done. The connection appears on the Apps page.

You can also connect from where you need the app. The Action node’s picker shows Connect on an app that isn’t connected yet. The agent editor’s Add a connection lists apps under Not connected. The assistant can offer a card with a Connect button. Each opens the same Super Connect window for that one app.

Read the Apps page

Each row is one connection.

Column	What it shows
App	The app, and what is connected: a bot user, a user account, an app installation or an API key
Account	The connected account’s name and email
Workspace	Whose workspace it reaches, such as a Slack team, a Jira site or a Google domain
Access	How many scopes it holds, and what its event triggers watch
Health	Its health, and when its sign-in was last refreshed
Connected	The date it was connected

Press a row to open its details: when the access expires, the next refresh, the last failure and its error, what it watches, the app’s own account facts, and the full list of scopes.

Health

Health	Meaning
healthy	The sign-in works
refreshing	Super Connect is renewing the sign-in
failing	The last renewal failed and Super Connect tries again; the details show the error
needs reauthorization	Super Connect stopped trying; an admin must reauthorize the connection

The builder flags an App event trigger whose connection is failing or needs reauthorization, and the dashboard lists stopped triggers. Once a connection needs reauthorization, its triggers stop and the steps and agents that use it fail until an admin reauthorizes it.

Reauthorize a connection

1. Open the Apps page.
2. Press … at the end of the connection’s row.
3. Press Reauthorize.
4. Sign in to the app again in the Super Connect window.

Reauthorizing repairs the connection in place. It keeps the same connection, so workflows, triggers and agent grants need no change, and Super Connect retries its failed event subscriptions. In the builder, a broken App event trigger offers Reconnect, which does the same.

Disconnect a connection

Press … at the end of the connection’s row, then Disconnect.

Caution

Disconnect takes effect at once and asks no confirmation. Triggers on the connection stop, Action steps that name it fail, and agents show the grant as Connection removed.

Connecting the same account again creates a new connection. Choose it on the triggers and Action nodes that named the old one, then publish again.

Which connection a step uses

An Action node’s Connection is either a named connection or Automatic. Automatic uses the connection whose event started the run when it belongs to the same app, otherwise the app’s only connection. With several connections to the same app and none named, the step fails with “Choose a connection”. See Action.

Events and your plan

An App event trigger listens on one connection for one kind of event. Super Connect keeps that as an app subscription, shared by every live trigger with the same connection, event and filter. Your plan caps how many active app subscriptions you have: 2 on Free and 25 on Pro. Publishing refuses to go over. See Triggers and Allowances.

The apps

GitHub, Gmail, Google Calendar, Google Drive, Google Search Console, Google Sheets, HubSpot, Jira, Notion and Slack.