Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 04:45 UTC
type: "guide" title: "Move a Composio Integration from Prototype to Production" description: "Public guidance for production user identity, environment isolation, authentication, sessions, and trigger delivery." category: "getting-started" visibility: "public" timestamp: "2026-08-24T00:00:00Z" tags: - "production" - "deployment" - "users" - "projects" - "authentication"
- "sessions"
Move a Composio Integration from Prototype to Production
Replace example user IDs with stable application user IDs
Create sessions and connected accounts with a stable identifier from the
application database, such as a UUID or primary key. Do not use an email
address that can change, and never use default in production. Composio uses
the user ID to isolate connections and tool calls, so each application user
must resolve to the same Composio user ID across sessions.
Isolate environments with separate Composio projects when needed
A Composio project scopes its API keys, connected accounts, auth configs, and webhooks. Use separate projects for development, staging, and production when those resources must not overlap. Use the API key for the intended project in each deployment, and create environment-specific auth configs when the OAuth apps, scopes, or provider credentials differ.
Use managed auth in production, and your own OAuth app when you need dedicated limits
Composio-managed OAuth apps work in production. Because the OAuth app is shared, you may run into shared provider rate limits as your usage grows. For higher volume, we recommend a custom auth config with your own OAuth app. It also gives you your application's OAuth brand, custom scopes, a dedicated provider quota, different polling requirements, and custom instances. Both options keep connected-account credential storage and refresh in Composio. Pass the resulting auth config ID to the session; creating the config alone does not make the session use it.
Restrict the production session to the capabilities the agent needs
Set toolkit, tool, and behavior-tag filters when creating the session. For a
sensitive or deterministic workflow, prefer an explicit allowlist of exact
tool slugs. For a broader read-only agent, filter on readOnlyHint and disable
destructiveHint, then inspect the resulting tool set before rollout.
Reuse a stored session until the user or configuration changes
Store the session ID and restore it with composio.use(session_id) instead of
creating a new session for every turn. Create a new session for a different
user or a materially different setup, such as a new tool policy or auth-config
mapping. A session preserves its scoped runtime state, but it is not the
language model's conversation memory.
Test production trigger handling through the real webhook path
The local subscribe() stream is useful for inspecting events, but it bypasses
the production webhook handler and signature verification. Before rollout,
forward events to the real local handler or use a tunnel, verify the signed
payload with parse(), and then register the production HTTPS webhook URL for
the production project.