Documentation

Creating a Connection

1

Navigate to Connections

Open the Connections page from the left sidebar. You will see a list of all existing connections for your organization.

2

Click "Add Connection"

A dialog appears with a dropdown to select the service type — Gmail, Slack, GitHub, etc.

3

Choose the service

Select the integration you want to connect. The dialog updates to show the authentication method for that service.

4

Authenticate

For OAuth services, click Connect. A popup redirects you to the service's login page. Sign in and grant permissions. The popup closes automatically when authentication succeeds.

5

Name the connection

Give the connection a descriptive name (e.g., "Engineering Gmail" or "Sales Slack"). This name appears in node configuration dropdowns.

Multiple connections per service

You can create multiple connections for the same service. For example, connect both your personal Gmail and a shared team inbox as separate connections, then choose which one to use in each workflow node.

Connection Statuses

Each connection shows a status badge indicating its current health:

Status	Meaning	Action
Active	Credentials are valid and the connection is working.	None needed.
Expired	The OAuth token has expired and could not be auto-refreshed.	Click Reconnect to re-authenticate.
Failed	The last health check failed (API returned an error).	Check the service status or update credentials.
Disconnected	The connection was manually disconnected.	Click Reconnect to re-establish.

A91I runs automated health checks every 15 minutes. Tokens are refreshed proactively before they expire. If a refresh fails, the status changes to Expired and you are notified.

Managing Connections

Testing a Connection

Click the Test button on any connection row to verify it is working. The test makes a lightweight API call to the service (e.g., fetching the authenticated user profile) and reports success or failure.

Editing

Click the connection name to open its detail view. You can change the display name or update API keys. For OAuth connections, click Reconnect to re-authenticate with potentially different scopes or a different account.

Deleting

Click the delete icon and confirm. Deleting a connection removes the stored credentials permanently. Any workflow nodes using this connection will fail on next execution until a replacement connection is assigned.

Check workflows first

Before deleting a connection, search for workflows that use it. Reassign those nodes to a different connection to avoid broken automations.

Sharing Connections

By default, connections are private to the user who created them. You can share a connection with other members of your organization so they can use it in their workflows without creating their own.

1

Open the connection detail

Click on the connection name from the list.

2

Click Share

In the detail view, click the Share button. A dialog appears listing organization members.

3

Choose permissions

Select the users to share with and assign a permission level:

Use: The user can select this connection when configuring workflow nodes, but cannot view credentials or modify the connection.
Manage: The user can test, edit, and share the connection in addition to using it.
Admin: Full control, including the ability to delete the connection and modify sharing settings.

Troubleshooting

Expired Tokens

If a connection shows as Expired, click Reconnect to re-authenticate. This is most commonly caused by:

The refresh token expired (some providers have a limited lifetime).
The user revoked access in the service's settings.
The service's OAuth application was reconfigured.

Permission Errors

If a workflow node fails with a permissions error, the connection may not have the required scopes. Reconnect the service and ensure you grant all requested permissions during the OAuth flow.

Rate Limiting

Each integration has built-in rate limiting to prevent API throttling. If you hit a rate limit, the system will automatically retry with exponential backoff. For very high-volume workflows, consider spacing out executions or using a dedicated connection with higher rate limits.