Skip to main content
Connect Gmail, Calendar, GitHub, Slack, Notion and 1,600+ more apps through your own Composio project.

​
1. Create a Composio project and save its key

  1. Sign up at app.composio.dev and create a project.
  2. Copy the project’s API key.
  3. As the admin, open Settings → Integrations setup and paste it under Composio key.
You can also paste it during first-run setup, in the Tool keys box.

​
2. Set up the built-in integrations

If your Composio project has auth configs (Composio’s record of how users sign in to an app), GAIA fills in a match for each integration. Check them and click Save. For an empty integration:
  1. Click Set up automatically.
  2. Fill in any fields it asks for. Most apps ask for nothing.
  3. Click Set up.
No callback URL is needed in Composio.
Composio’s Google sign-in is fine for trying things out. To show your own app name on Google’s consent screen, create an OAuth client in the Google Cloud console. Create the auth config with those credentials in the Composio dashboard, and pick it here. Use the redirect URI Composio shows in the form. Enable each Google API you use in the same project.

​
3. Add any other app from the catalog

Click Browse Composio catalog in Settings → Integrations setup. Admins also see it on the integrations page.
Composio catalog dialog with a Search 1,600+ apps box, an All categories filter, and a list of apps: Gmail, GitHub, Google Calendar, Notion, Google Sheets and Slack marked Built in, not set up, Composio marked No sign-in and Supabase marked Available, next to an empty pane reading Pick an app to see what enabling it takes

The Composio catalog. Each app is marked Built in, Available or No sign-in

  1. Search for the app and pick it.
  2. Follow what the catalog says:
    Composio catalog searched for Attio, with Attio marked Available and its detail pane: 105 tools in crm, a description, the note Users sign in through Composio's own app. Nothing to fill in, a note that catalog apps have no triggers, and an Enable button

    Attio picked from the catalog: its users sign in through Composio, so there is nothing to fill in

  3. Click Enable.
The app appears on everyone’s integrations page right away. Users click Connect, and GAIA can use the app’s tools in chat and workflows.
Apps that need no sign-in, such as Hacker News, show No sign-in and can’t be enabled yet.To remove an app, open it in the catalog and click Remove. Its auth config and your users’ connections stay in Composio, so delete them there.
If you manage configuration in files, set COMPOSIO_KEY and map built-in integration ids to auth config ids:
An id saved in Settings → Integrations setup wins. The instance refuses to start if this names an integration that doesn’t use Composio, or gives an empty id. Catalog apps are configured in the app only.

​
Troubleshooting

Want to connect MCP servers instead? See MCP servers.