Providers & managing connections
This page lists the apps you can connect to Alfe by authorizing an account, and covers how to manage those connections once they exist.
Apps you can connect
Section titled “Apps you can connect”You can connect an account for each of these providers through the OAuth connect flow:
| Provider | What connecting enables |
|---|---|
| GitHub | Work with repositories, issues, pull requests, and code. |
| Notion | Read and search pages and databases; create and update entries. |
| Google Workspace | Gmail, Drive, Calendar, Docs, Sheets, Slides, and more. |
| Microsoft 365 | Outlook mail, calendar, and OneDrive. |
| Atlassian (Jira + Confluence) | Track issues and read/write documentation. |
| Xero | Accounting — invoices, contacts, and finances. |
| MYOB Business | Accounting — invoices, contacts, and finances. |
| Salesforce | Query and manage CRM records. |
Connecting any of these follows the same flow — see Connecting an account.
Channels use the same authorization
Section titled “Channels use the same authorization”Messaging channels such as Slack, Discord, and Microsoft Teams also connect by authorizing access, but they work a little differently: because Alfe uses per-agent identity, connecting one of these adds the agent to the platform as its own bot. Channels are covered under Integrations.
Some connections aren’t OAuth at all — for example a provisioned phone number for messaging. Those are set up from their own flows in the dashboard rather than by authorizing an existing account.
Managing a connection
Section titled “Managing a connection”Everything below happens in the Connections hub in the dashboard at app.alfe.ai. Open a connection to see its details and the actions available on it.
Give a connection a human-readable label so it’s easy to tell apart from others of the same provider — for example “Finance — Xero” versus “Ops — Xero”. This is just a display name and doesn’t affect access.
Reconnect
Section titled “Reconnect”If a connection’s access lapses — for example it expires or is withdrawn on the provider’s side — the hub flags it and offers Reconnect. Reconnecting reruns the approval flow to restore access while keeping the same connection, so everything pointing at it keeps working. See reconnecting.
Change the scope a connection lives at — for example to narrow an organization-wide account to a single team. Moving keeps the same connection and doesn’t require re-authorizing. See moving a connection.
Disconnect
Section titled “Disconnect”Disconnecting removes the connection and revokes Alfe’s stored access to that account. Agents that were relying on it lose access to that app immediately, so disconnect only when you’re sure nothing still needs it. If you later want the account back, connect it again from scratch.
For messaging channels and paid connections (such as a provisioned phone number), disconnecting also tears down the associated setup — the hub confirms this before you proceed.
Connection status
Section titled “Connection status”Each connection shows a status so you can see its health at a glance:
- Active — connected and usable.
- Pending — setup is still finishing (used by connections that provision something in the background, such as a phone number).
- Expired — access has lapsed and needs a Reconnect.
- Revoked — access was withdrawn; reconnect to restore it.
- Error — Alfe hit a problem using the connection; reconnecting usually clears it.
When a connection isn’t Active, the hub surfaces the action that fixes it — most often Reconnect.
Next steps
Section titled “Next steps”- Walk through the connect flow: Connecting an account.
- Understand where a connection is available: Connection scopes.
- Turn a connected account into agent capabilities: Integrations.