Integrations
Integrations allow AI workers to read from and act in external services. Connect only the services each workflow needs, such as Gmail, Google Drive, Slack, Notion, or GitHub. Creating a connection profile is not enough; assign the integration to the target AI worker as well.
Overview
Connect Google, Slack, Notion, GitHub, and other services to AI workers.
Basics
Connection units
Integrations are managed by service or profile. Use OAuth connections, API-key connections, MCP servers, Composio-compatible tools, and native integrations where appropriate. If multiple accounts are used, name profiles clearly so each worker uses the intended account.
Permission model
Grant the minimum permissions needed. Do not give write access to workflows that only need reading, and write confirmation rules into worker instructions for sends, deletes, and updates. Do not let one user reuse another user's OAuth profile without ownership.
Using integrations in workers
Connecting a service is not enough; assign it from the AI worker's Integrations screen. The screen shows configured MCPs, custom MCPs, Composio/native profiles, and enabled tools before saving. Also describe when to use the integration, which service to prioritize, and which actions require confirmation.
Troubleshooting
If an integration fails, check expired auth, wrong account, missing permissions, worker assignment, MCP configuration, profile IDs, and secret reference names. After reconnecting, re-test representative read, create, and update operations.
Checklist
- Confirm the connected service and account are correct.
- Check that only required permissions are granted.
- Test the actual read, create, or update actions the worker needs.