Integrations (Gmail, Calendar, Slack, Notion, ...)

Overview

Chelar lets your assistant act on your external accounts — read Gmail, create calendar events, post to Slack, update Notion pages, open GitHub issues, and more. The connection goes through Composio, which brokers OAuth with 1000+ apps so you don't have to set up each one from scratch.

Setup takes about three minutes.

How it works

┌──────────────┐      ┌─────────┐      ┌──────────────┐
│ Your         │──MCP→│ Composio│──────│ Gmail, Slack,│
│ assistant    │      │         │      │ Calendar, ...│
└──────────────┘      └─────────┘      └──────────────┘

• Your assistant connects to Composio over MCP (Model Context Protocol) — a standard protocol for exposing tools to AI agents.
• Composio holds the OAuth tokens for each app you've connected in its dashboard and turns them into callable tools for your assistant.
• Chelar writes Composio's MCP endpoint into your assistant's config, authenticated with your consumer API key. We never see the tokens to your third-party apps — they stay in Composio.

Setup

Step 1 — Create a Composio account

Go to composio.dev and sign up. The free tier gives you 20,000 tool calls per month, which is more than enough for individual use.

Step 2 — Get your consumer API key

1. Open connect.composio.dev
2. In the install list, click the MCP card
3. Select the API Key tab (not OAuth)
4. Copy the key — it starts with ck_

Step 3 — Connect your apps in Composio

In the Composio dashboard, go to Connect Apps and sign in to the services you want your assistant to use:

• Gmail — read your inbox, send email, label messages
• Google Calendar — list, create, and update events
• Slack — post messages, read channels
• Notion — read and update pages
• GitHub — open issues, read repos
• Linear — create and manage issues
• 1000+ more at composio.dev/apps

Every app you connect in Composio becomes available to your assistant as soon as you paste the API key in the next step.

Step 4 — Paste the key in Chelar

1. In Chelar, open Integrations from the left nav
2. In the "Connect via Composio" card, paste your ck_... key
3. Click Save and connect

Your assistant container restarts (~30 seconds). After that, the agent can use any toolkit you've connected in Composio.

Testing the connection

Once connected, open a chat with your assistant and ask:

What tools do you have from Composio?

The assistant will list the toolkits you've connected (Gmail, Calendar, Slack, etc.). Try a concrete action:

Search my Gmail for the most recent message from Stripe.

If everything works, the assistant will fetch the message via Composio and summarize it. If it says it can't connect, double-check you pasted the ck_... key (not ak_...) and that you've connected Gmail in the Composio dashboard.

Usage & limits

• Composio's limits apply, not Chelar's — we don't meter your tool calls. The free tier includes 20k calls/month, which refreshes monthly. Upgrade your Composio plan if you need more.
• Your Chelar plan gates whether Integrations are available. BYO Composio is on every plan (including Trial).

Disconnecting

Click Disconnect on the Integrations page. Your assistant restarts (~30s) without MCP access. Your Composio-side tokens are unaffected — they stay until you revoke them in your Composio dashboard.

Troubleshooting

Agent says it has no tools from Composio

• Check that you pasted the ck_... consumer key, not ak_... admin key
• Make sure you've connected at least one app in the Composio dashboard
• Wait ~30 seconds after saving for the container to restart

"401 Unauthorized" in logs

The key format is wrong. MCP needs the consumer key starting with ck_. Regenerate from connect.composio.dev → MCP → API Key tab → Regenerate.

Tool calls fail mid-execution

Usually means a third-party token expired (e.g. Gmail re-authentication needed). Go to your Composio dashboard, reconnect the app, and try again. No Chelar-side change needed.

FAQ

Does Chelar see my email / calendar data? No. OAuth tokens stay in Composio's database. Tool results flow from Composio → your assistant container → your chat. The tenant container sees the returned data (an email body, for example), but Chelar's control plane does not — the connection goes direct from the container to Composio.

Can I use my own MCP server instead of Composio? Not via this panel yet. The current UI is Composio-specific. We plan to add generic MCP server support when we see demand — open an issue if this matters to you.

Do I need to pay Composio? The free tier covers 20k calls/month. If you're a heavy user, Composio charges per toolkit per month. See composio.dev/pricing.

Is a managed integration coming (no Composio account needed)? Yes — it's labelled "Coming soon" in the Integrations page. We're finishing the last pieces. Managed integrations will sign in via OAuth from the Chelar dashboard directly, no external account required.