Tool Integration Platforms
Use Composio with CrewAI
Composio connects to CrewAI through a built in by the framework vendor path (crewai_tools ComposioTool). This page records what that connection looks like and links the evidence behind it.
Pairing facts
Why this pairing
Tool platform for AI agents with pre-authenticated toolkits, per-user sessions, managed authentication, triggers, and a sandboxed workbench across a large app catalog.
Best for: Agent apps that need many SaaS tools with per-user OAuth, API key handling, tool search, triggers, and framework adapters, without building each integration and auth flow from scratch.
Not ideal for: Teams that need raw isolated Linux computers for arbitrary code execution as the primary primitive, or that want to self-host the whole integration platform under a permissive license with no hosted dependency.
Configuration
from crewai_tools import ComposioToolSource: https://github.com/crewaiinc/crewai/issues/3544. Examples use placeholders only.
Evidence
The fetched CrewAI repository issue import list includes ComposioTool in crewai_tools.
https://github.com/crewaiinc/crewai/issues/3544
Compatibility here means the cited page documents the pairing. It does not mean AgentsUse benchmarked the combination or that every version works unchanged. Pin versions, run the tool on a small job first, and review the first outputs before widening access.
Watch for
- The free tier is an included allowance, not unlimited use. Past the included amounts, tool calls, triggers, managed app usage, and Instant Tools can bill separately by mode.
- Composio-managed apps have lower allowances and count toward free tier limits on the pricing page, which advises using your own OAuth app for scaling.
- The platform is hosted and session centric. Teams wanting a fully self-hosted integration runtime or raw sandbox computers will find the model opinionated.