How integrations work
An integration turns on when an agent has what it needs: a channel, a connection, or a direct install. You never install tools for a Slack bot or a GitHub account by hand. Alfe works that out from the channels and connections the agent can see.
The lifecycle: install → connect → active
Section titled “The lifecycle: install → connect → active”Only installable integrations have an install step. Here’s how each family reaches active:
| Family | What you do | What turns it on |
|---|---|---|
| Channel | Finish setup in the agent’s Channels tab. | An active channel on that agent. |
| Connection | Add the account in the Connections hub. | A working connection the agent can see. |
| Installable integration | Select Install in the agent’s Integrations tab. | The install itself, once any settings are filled in. |
Once it’s active, the agent’s runtime picks up the integration’s tools, and the agent can use them in its work. The agent has to be online for that to happen.
Removal mirrors setup. Disconnect the channel or connection, or remove the installation. When nothing else on the agent needs the tools, Alfe cleans them up.
For the steps to connect an account, see Connect an account.
Per-agent identity
Section titled “Per-agent identity”A defining principle on Alfe is per-agent identity. Each agent that joins Slack or Teams does so as its own bot, with its own credentials, never a shared global one. That means:
- Two agents can join the same workspace as separate bots.
- Removing one agent’s channel doesn’t affect another agent.
- Credentials are stored encrypted and tied to the agent that owns them.
Connections work a little differently, because you choose how widely to share them. Keep an account on one agent, or share it across a team.
Scopes
Section titled “Scopes”Where something can live depends on its family:
- Connections — at your organization, a team, a project, or a single agent. Agents inherit connections from the scopes above them. See Connection scopes.
- Channels — on one agent only.
- Installable integrations — on one agent.
See Identity and scopes for how scopes work across the platform.
Runtime support
Section titled “Runtime support”Not every capability runs on every runtime. An agent’s runtime decides what’s available:
- Most connections run on every runtime. Google Workspace and Telegram are the exceptions.
- Most channels need OpenClaw. Slack also works on terminal runtimes, because its adapter runs on Alfe’s side.
- Some installable integrations need specific runtimes.
The integrations overview lists support for each one, and runtimes explains the options.
How integrations are priced
Section titled “How integrations are priced”Integrations fall into three shapes:
- Free — most channels, connections, and integrations. You only pay for what the agent uses, such as models.
- Usage-based — WhatsApp, Memory, and News Search meter what they consume. Usage draws from your shared credit pool.
- Bring your own key — integrations such as Stripe and Semrush, and the Vast.ai connection, use your account with that vendor. The vendor bills you directly.
A phone number has its own monthly charge. See How voice is billed. For current rates, see Live pricing.
Who can set up integrations
Section titled “Who can set up integrations”A person or an agent can do it, but not everything is open to both:
- A person can set up all three families from the dashboard or the desktop app.
- An agent can install and configure installable integrations over MCP or the Agent API. For connections, it generates an OAuth link that a person must approve.
Direct install requests for a channel or connection are refused, because those activate from their own setup. See Managing integrations.