https://backend.composio.dev/api/v3.1), using a project API key from the Composio dashboard. ConfigView sends only GET requests, plus a few POST calls that only read usage counts. It never creates, changes or deletes anything in Composio.
You will end up with 1 required secret (COMPOSIO_API_KEY) and 1 optional secret (COMPOSIO_ORG_API_KEY) in ConfigView when setup is complete.
Scope of this integration today. ConfigView answers “which apps can our AI agents reach, and as whom”: the connected accounts (app, end user, status, auth config), the auth configs (auth scheme, Composio-managed or your own credentials, tool allow-lists), MCP servers and their tools, triggers, webhook subscriptions, projects, and tool-call counts per user, app and connected account. It does not read tokens, credentials, tool execution logs, tool arguments or results, or trigger payloads.
What you need
- A Composio project and access to its dashboard
- The project API key. Optional: the organization API key, to cover every project in the organization
Step 1: Open the Composio page in ConfigView
Open ConfigView in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/composio
Step 2: Copy the API keys
- In the Composio dashboard open your project and go to Settings > API Keys
- Copy the project API key. Composio documents no read-only key, so the key can do more than ConfigView uses; ConfigView only ever reads.
- In the ConfigView tab paste it into
COMPOSIO_API_KEYunder Credentials and save - Optional: if you want every project in the organization and usage by project, copy the organization API key and save it as
COMPOSIO_ORG_API_KEY. Leave it empty and the two organization collectors skip.
Step 3: Connect and verify
- Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret, then one page of connected accounts and auth configs, and the organization projects if the organization key is set.
- 401. The key is wrong, revoked, or belongs to a different project.
- 403 or 404. The key cannot read that area.
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
End user ids.user_id is whatever your own application passed to Composio when it connected the account. It is often a work email but does not have to be, so ConfigView does not treat it as a person it can match to your directory.
Tool allow-lists. An auth config with no restricted tools and no execution tool list lets agents run every action the app offers. ConfigView lists these. How Composio treats an empty list is not spelled out in its reference, so confirm it on your first run.
Usage is counts only. Tool-call counts cover the last 30 days, grouped by user, app or connected account. ConfigView never calls Composio’s tool execution log endpoints, because they carry request and response payloads.
Triggers. Composio does not return an app for a trigger. ConfigView takes the first word of the trigger name as a hint and joins the connected account for the real app.
Rate limit. Composio allows 2,000 requests a minute per organization on Hobby (10,000 on Pro), shared by every endpoint, and answers HTTP 429 with Retry-After. ConfigView paces itself at 300 requests a minute and waits as long as Composio asks.
What isn’t collected
- OAuth tokens, API keys,
state,data,credentials,shared_credentialsand proxy settings - MCP server URLs (only the host) and webhook URLs (only the host) and signing secrets
- Trigger configuration and event payloads
- Tool execution logs, tool arguments and results