How to Use Composio with Claude Co-work to Connect 1,000+ Apps to Your AI Agents
Composio gives Claude Co-work access to 1,047 apps via OAuth. Learn how to connect Gmail, Xero, Notion, and more to your scheduled cloud agents.
Why Connecting AI Agents to Real Apps Is Harder Than It Looks
Building a Claude-powered agent is the easy part. Getting that agent to actually do things — send an email, update a spreadsheet, create an invoice — requires authentication, API wrappers, token management, and error handling for every single app you want to connect.
That’s where most AI agent projects stall.
Composio solves this problem by giving your agents a unified integration layer with 1,047+ app connections, all handled via OAuth. When combined with Claude Co-work inside MindStudio — the platform’s scheduled cloud agent environment — you can build agents that autonomously connect to Gmail, Xero, Notion, Slack, GitHub, and hundreds of other tools without managing a single API credential yourself.
This guide covers exactly how to set that up.
What Composio Actually Does
Composio is an integration infrastructure tool built specifically for AI agents. Unlike general-purpose automation tools, it’s designed with agent use cases in mind — meaning it exposes app actions as callable tools that LLMs can reason about and invoke.
Here’s what makes it different from just rolling your own API calls:
- Managed OAuth flows — Composio handles token exchange, refresh logic, and scope management for every supported app. You authenticate once, and your agent can call app actions without ever touching credentials.
- Typed action schemas — Every integration exposes structured actions (e.g.,
GMAIL_SEND_EMAIL,NOTION_CREATE_PAGE,XERO_CREATE_INVOICE) with defined inputs and outputs. This makes it easy for Claude to understand what each action does and how to call it correctly. - Multi-tenant auth — If you’re building agents for multiple users or clients, Composio manages separate authentication sessions per user so each person’s data stays isolated.
- 1,047+ supported apps — The catalog covers CRMs, accounting tools, project management platforms, communication apps, developer tools, and more.
Plans first. Then code.
Remy writes the spec, manages the build, and ships the app.
In short: Composio is the layer that lets your Claude agent say “send this email to that person” and have it actually happen.
What Claude Co-work Means in MindStudio
MindStudio is the no-code platform where you build and deploy AI agents. Within MindStudio, Claude Co-work refers to using Claude (Anthropic’s model) as the reasoning engine inside a scheduled background agent — an agent that runs automatically on a timer, processes data, and takes actions without anyone clicking a button.
These cloud agents are useful for things like:
- Sending weekly digest emails from your inbox
- Syncing CRM records every morning
- Creating draft invoices in Xero from new project entries
- Posting summaries to Slack at the end of each day
The “Co-work” framing matters because these aren’t one-shot prompts. They’re agents that run continuously on a schedule, make decisions based on current data, and interact with multiple apps in sequence. Claude handles the reasoning; Composio handles the connections.
MindStudio provides the builder, the scheduler, the deployment infrastructure, and the Composio integration — all in one place.
Before You Start: Prerequisites
Before setting up Composio with Claude Co-work, make sure you have:
- A MindStudio account — Free to start at mindstudio.ai
- A Composio account — Sign up at composio.dev (free tier available)
- Access to the apps you want to connect — Gmail, Xero, Notion, or whichever tools you’re targeting
- A basic understanding of what you want the agent to do — Having a clear use case makes configuration much faster
You don’t need to write code, manage API keys for each app, or set up OAuth servers yourself. Composio and MindStudio handle that infrastructure.
Step 1: Set Up Your Composio Account and Connect Your First App
Create Your Composio API Key
Log into Composio and navigate to your dashboard. Under Settings → API Keys, generate a new key. Copy it somewhere safe — you’ll need it when connecting Composio to MindStudio.
Connect an App via OAuth
In the Composio dashboard, go to Integrations and search for the app you want to connect — for example, Gmail.
- Click on Gmail and select Add Connection.
- Composio will redirect you to Google’s OAuth consent screen.
- Sign in with the Google account you want the agent to access.
- Grant the requested permissions (read/send email, etc.).
- You’ll be redirected back to Composio with a confirmed connection.
Repeat this for each app: Xero, Notion, Slack, GitHub — whatever your agent needs. Each connection creates an authenticated session that Composio manages on your behalf.
Note Your Entity ID
Composio assigns each authenticated user an Entity ID — a unique identifier that links your OAuth connections to your agent’s calls. The default is default, but if you’re building for multiple users, you’ll assign unique entity IDs per user. Keep this value handy.
Step 2: Build Your Scheduled Agent in MindStudio
Create a New AI Worker
In MindStudio, click New App and select AI Worker as the agent type. This creates a background agent that can run on a schedule.
Name your agent something descriptive — for example, “Weekly Gmail Digest” or “Xero Invoice Automation.”
Set Claude as Your Model
Other agents ship a demo. Remy ships an app.
Real backend. Real database. Real auth. Real plumbing. Remy has it all.
In the model selection panel, choose Claude (Sonnet or Opus depending on the complexity of reasoning your agent needs). Claude is well-suited for agentic tasks because it follows multi-step instructions reliably and handles tool calls cleanly.
Configure the Schedule
Under the Trigger settings, set when the agent should run:
- Every day at 8am
- Every Monday at 9am
- Every hour
- Custom cron expression
MindStudio handles the scheduling infrastructure — you don’t need to set up cron jobs or keep anything running locally.
Step 3: Connect Composio Inside MindStudio
Add the Composio Integration
In your MindStudio agent’s workflow, open the Integrations panel and search for Composio. Add it as a connected service and paste in your Composio API key.
This connects your MindStudio agent to your Composio account, giving it access to all your authenticated app connections.
Define Which Actions the Agent Can Use
In the agent’s system prompt or tool configuration, specify which Composio actions the agent is allowed to call. For example:
GMAIL_LIST_THREADS— retrieve recent email threadsGMAIL_SEND_EMAIL— send an email from the connected accountNOTION_CREATE_PAGE— create a new page in a Notion workspaceXERO_CREATE_INVOICE— generate an invoice in Xero
You can also give the agent access to the full catalog and let Claude decide which tool to call based on context — though scoping it to relevant actions gives you more predictable behavior.
Write the Agent’s Instructions
This is where you tell Claude what to do on each run. Keep it specific and sequential. A good agent prompt for a Gmail digest might look like:
“Each time you run, retrieve the last 20 email threads from Gmail. Summarize the key action items from each thread. Compile them into a clear digest and send it to [email address] with the subject line ‘Daily Email Summary — [Date]’.”
For a Xero invoicing agent:
“Check the connected Notion database for any project entries marked ‘Ready to Invoice’ that don’t yet have a Xero Invoice ID. For each one, create an invoice in Xero using the project name, client name, amount, and due date from the Notion entry. Then update the Notion record with the new Xero Invoice ID.”
Claude reads these instructions, decides which Composio tools to call, calls them in the right order, and handles the outputs — all without you intervening.
Step 4: Test Before Scheduling
Before turning on the schedule, run the agent manually to confirm everything works.
Check the Execution Log
MindStudio shows you a full execution trace — each step Claude took, which tools it called, what the inputs and outputs were, and whether anything failed. This is the fastest way to catch problems.
Common issues to look for:
- Auth errors — The Composio connection might have expired or the wrong entity ID was used. Reconnect the app in Composio.
- Scope errors — The OAuth permissions granted might not include what the agent is trying to do. Reconnect with broader scopes.
- Hallucinated tool names — Claude might occasionally try to call a tool that doesn’t exist. Fix this by being more explicit in the system prompt about which actions are available.
- Missing required fields — Some Composio actions require specific fields that Claude might not fill in correctly. Add examples to your prompt showing the expected format.
Everyone else built a construction worker.
We built the contractor.
One file at a time.
UI, API, database, deploy.
Run a Dry Run
If your agent sends emails or creates records, add a “dry run” mode during testing — have Claude describe what it would do without actually doing it. Once the logic looks right, switch to live mode.
Real Use Cases: What You Can Build
Gmail + Notion: Inbox-to-Task Pipeline
This agent checks Gmail every morning for emails containing specific keywords (e.g., client names, project codes). For each match, it creates a task in Notion with the email subject, sender, summary, and a link to the thread. Useful for anyone who manages client work through email and wants it automatically tracked.
Xero + Slack: Invoice Status Alerts
Connect Xero and Slack to build an agent that runs daily and checks for overdue invoices. For each invoice past its due date, it posts a Slack message to the finance channel with the client name, amount, and number of days overdue. No more manually checking Xero every day.
GitHub + Linear: PR-to-Issue Sync
When a pull request is opened on GitHub with a specific label (e.g., “needs-ticket”), this agent automatically creates a corresponding issue in Linear with the PR title, description, and a link back to GitHub. Keeps engineering teams in sync across tools.
HubSpot + Gmail: Personalized Outreach at Scale
An agent that pulls a list of leads from HubSpot who haven’t been contacted in 30+ days, generates a personalized follow-up email for each using Claude, and sends them via Gmail — all on a weekly schedule. The emails reference the lead’s company, last interaction, and any notes in HubSpot.
Airtable + Xero: Expense Reconciliation
This agent pulls expense records from an Airtable base and matches them against transactions in Xero. Discrepancies are flagged in a separate Airtable view for manual review. Cuts down the time spent on monthly reconciliation significantly.
How MindStudio Makes This Easier
If you’re building Claude-powered agents that connect to external apps, MindStudio is the environment where all of this comes together cleanly.
You get:
- A visual builder — No code required to configure agents, set schedules, or wire up Composio
- 200+ AI models — Switch between Claude, GPT-4o, Gemini, and others without separate accounts or API keys
- Composio integration built in — No custom middleware or webhook setup needed
- Execution logs and monitoring — See every agent run, debug failures, and track usage
- Scalable scheduling — Run agents every minute or once a week, with no infrastructure to manage
MindStudio positions itself as purpose-built for agentic workflows — not just simple trigger-action automations, but agents that reason across multiple steps and make decisions based on data. That’s exactly what Composio + Claude enables.
For teams that want to deploy these agents quickly — without engineering overhead — MindStudio handles everything from the builder to the runtime. You can try it free at mindstudio.ai.
If you want to explore what’s possible before building from scratch, MindStudio also has pre-built agent templates covering common automation use cases.
Frequently Asked Questions
Remy doesn't write the code. It manages the agents who do.
Remy runs the project. The specialists do the work. You work with the PM, not the implementers.
What is Composio and how does it work with AI agents?
Composio is an integration platform built for AI agents. It connects your agent to 1,047+ apps — Gmail, Slack, Notion, Xero, GitHub, and more — via OAuth, so the agent can call app actions directly without you managing API credentials. Each app integration exposes typed actions (like GMAIL_SEND_EMAIL or NOTION_CREATE_PAGE) that an LLM like Claude can call as tools during a workflow.
Does Composio work with Claude specifically?
Yes. Composio’s action schemas are compatible with Claude’s tool use (function calling) API. Claude can read the available actions, decide which ones to use based on context, and call them with the right inputs. This works particularly well in agentic settings where Claude needs to chain multiple actions together.
What apps does Composio support?
Composio supports over 1,047 apps as of its current catalog. This includes major categories like:
- Email & calendar: Gmail, Outlook, Google Calendar
- Project management: Notion, Linear, Asana, Jira
- CRM: HubSpot, Salesforce, Pipedrive
- Accounting: Xero, QuickBooks
- Communication: Slack, Discord, Microsoft Teams
- Developer tools: GitHub, GitLab, Jira
- Storage: Google Drive, Dropbox, Box
Is OAuth secure when using Composio?
Composio uses standard OAuth 2.0 flows for authentication, which means your credentials are never stored in your agent’s code or prompts. You authenticate directly with each app (e.g., Google, Xero), and Composio receives and manages the access tokens. Token refresh is handled automatically. This is more secure than storing API keys in environment variables and significantly easier to manage at scale.
Can I use Composio with agents that run for multiple users?
Yes. Composio supports multi-tenant authentication through entity IDs. Each user gets a unique entity ID, and their OAuth connections are stored separately. When your agent runs on behalf of a specific user, it passes that user’s entity ID to Composio, which routes the action through that user’s authenticated session. This is essential for any SaaS or client-facing agent.
What’s the difference between using Composio versus building my own API integrations?
Building your own integrations means writing OAuth flows, managing token refresh, handling API rate limits, and maintaining wrappers for every app you want to connect. Composio abstracts all of that. For most teams, Composio saves weeks of engineering work per integration and eliminates ongoing maintenance as APIs change. The tradeoff is that you’re relying on Composio’s catalog — if an app isn’t supported, you’d still need to build a custom integration.
Key Takeaways
- Composio gives Claude-powered agents access to 1,047+ apps via OAuth — no API credential management required.
- Claude Co-work in MindStudio refers to scheduled background agents that use Claude to reason and act across connected tools automatically.
- Setup involves three things: connecting apps in Composio, building the agent in MindStudio, and writing clear instructions for Claude.
- Real use cases include Gmail digests, Xero invoice automation, GitHub-to-Linear sync, and HubSpot outreach pipelines.
- MindStudio handles the infrastructure — scheduling, execution, logging, and Composio integration — so you can focus on what the agent should do, not how to run it.
Remy doesn't build the plumbing. It inherits it.
Other agents wire up auth, databases, models, and integrations from scratch every time you ask them to build something.
Remy ships with all of it from MindStudio — so every cycle goes into the app you actually want.
For teams that want agents that actually work — not just chat — connecting Composio to Claude via MindStudio is one of the fastest paths there. Start building free at mindstudio.ai.
