Aleph

Connections

Some agents need access to apps such as GitHub, Slack, Gmail, or Notion. Those requirements are declared in the agent bundle as Connections. You authorize them once for your workspace scope; Aleph then exposes the matching tools during agent turns.

Connections are separate from Channels. Channels deliver chat through bots and messaging platforms you own (Discord, Telegram, Slack, WhatsApp, Teams, and more). Connections authorize the agent to use third-party apps through Connect — even when the app name overlaps (for example GitHub as a Channel vs GitHub as a Connection).

Who owns the connection

Connections belong to the agent's dashboard scope:

  • Personal agents share Connections across agents you own personally.
  • Organization agents share Connections for that organization.
  • Team agents share Connections for that team.

Authorizing GitHub once in a scope lets every agent in that scope that declares GitHub use it.

Connect an app

  1. Open the agent and choose Connections in the management sidebar, or finish the create/edit/install/clone wizard through the Connections step after Vault.
  2. For each required app, choose Connect and complete the provider sign-in in the new tab.
  3. Return to Aleph and wait for status to show Connected (the page refreshes automatically).

If a required Connection is missing, Aleph shows a configuration warning and blocks turns that need that app until you connect it.

If a provider revokes or expires its credentials, choose Reconnect. Aleph refreshes that existing Connection and opens the provider's authorization flow when another sign-in is required. Return to Aleph after authorization finishes; you do not need to disconnect the app first.

Bundles that declare Connections

Creators may include an optional connections.toml in the bundle. Example:

[[connections]]
id = "github"
required = true

Supported toolkit ids include github, slack, gmail, notion, googlecalendar, linear, jira, and 100+ other apps that Aleph can Connect without custom OAuth setup. Upload rejects unknown ids. Agents without connections.toml show an empty Connections page and do not require app OAuth.

After installing or cloning

Installations and clones never copy Connections. Connect required apps again in your own scope before enabling an agent that depends on them. Do not paste personal access tokens into chat or the Vault for apps that use Connections.