Overview
Ready-made connections to well-known services, from registering in the organization to use by the agent.
Integrations are connections to services the platform already knows how to talk to. Unlike MCPs, you don't describe the protocol: you pick the service from a list and provide the access.
Like MCPs, they follow the path of a catalog in the organization and activation in the workspace.
Register in the organization
Organization › Integrations opens for Superadmin and Admin, with two tabs:
- Available: the catalog of integrations the platform knows that haven't been registered yet.
- Installed: the ones the organization has already registered and can distribute to workspaces.
To register one, open Available and click Install on the service card. There is no form at this stage: the integration goes straight to Installed. The access it needs is provided later, when each workspace installs it.
When the Available tab shows up empty, every known integration has already been registered in this registry.
Associate with a workspace
The association is made under Organization › Workspaces: open the workspace and, in the Integrations tab, turn on the card's switch. Its state goes from Inactive to Active. Associating and dissociating are reversible actions.
In the narrow bar on the left, click Organization.
Turn it on in the workspace
Workspace › Integrations has the same two tabs, Installed and Available, applied to what the organization associated with this workspace.
This screen is accessible only to the workspace Owner. No other role reaches it, not even read-only. A Curator building an Agent sees the integration in the form's list, but can't turn it on. It has to be turned on by someone with that role.
When installing in the workspace, the window asks for a name, a description and the credentials the integration requires. Integrations that depend on authorization at the source service open the consent flow at this point.
Hand it to an agent
Turning it on in the workspace doesn't hand the integration to any Agent. Each Agent checks what it can call in the Integrations section of its own form.
Workflows also reach integrations, through the canvas Integration node.
Name and description
The organization registry's action menu lets you edit a registered integration's name and description.
Use it when the same integration is registered more than once, pointing to different environments: the catalog's default name doesn't tell one from the other.
Remove
Turning off an integration in the workspace cuts off access for the Agents and Workflows that depended on it. The failure shows up at the time of use, not at the time of removal.
Next steps
- Keep the access they use in Credentials.
- Compare with the tool server path in MCPs.