> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Composio setup

ConfigView reads your Composio project (the platform that gives AI agents access to third-party apps) through the Composio **v3.1 API** (`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

1. In the Composio dashboard open your project and go to **Settings > API Keys**
2. Copy the **project API key**. Composio documents no read-only key, so the key can do more than ConfigView uses; ConfigView only ever reads.
3. In the ConfigView tab paste it into `COMPOSIO_API_KEY` under **Credentials** and save
4. 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.

A project key covers one project. Covered projects are the ones whose key you add.

***

## Step 3: Connect and verify

1. Click **Connect**. ConfigView creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Connected accounts** | Each account an agent can act through: app, end user, status, auth config, shared or private. |
| **Auth configs** | How agents sign in per app and which tools they may run. |
| **MCP servers** | MCP servers, the apps behind them and their allowed tools (host only). |
| **Triggers** | Trigger instances, their app, end user and destination host. |
| **Webhook subscriptions** | Destination host and event names. |
| **Projects** | All projects in the organization. Needs the organization key. |
| **Tool calls by user / app / connected account** | Call counts over the last 30 days. |
| **Tool calls by project** | Call counts per project. Needs the organization key. |

2. 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.

If a check fails:

* **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 a `run_at` column and keeps only the newest run.

| Table | Source | Key Columns |
| - | - | - |
| `composio_connected_accounts` | `GET /connected_accounts` | account\_id, user\_id, toolkit\_slug, status, auth\_scheme, auth\_config\_id, is\_composio\_managed, account\_type, created\_at, updated\_at |
| `composio_auth_configs` | `GET /auth_configs` | auth\_config\_id, name, toolkit\_slug, config\_type, auth\_scheme, is\_composio\_managed, status, connection\_count, restricted\_tools, execution\_tools |
| `composio_mcp_servers` | `GET /mcp/servers` | server\_id, name, url\_host, toolkits, allowed\_tools, instance\_count |
| `composio_triggers` | `GET /trigger_instances/active` | trigger\_id, trigger\_name, connected\_account\_id, user\_id, trigger\_type, egress\_host, is\_disabled |
| `composio_webhook_subscriptions` | `GET /webhook_subscriptions` | subscription\_id, url\_host, webhook\_version, events |
| `composio_projects` | `GET /org/owner/project/list` | project\_id, name, owner\_email, triggers\_enabled, is\_deleted |
| `composio_usage_by_user` | `POST /project/usage/tool_calls` | user\_id, tool\_call\_count, event\_count, window\_start, window\_end |
| `composio_usage_by_toolkit` | `POST /project/usage/tool_calls` | toolkit\_slug, tool\_call\_count, event\_count |
| `composio_usage_by_account` | `POST /project/usage/tool_calls` | connected\_account\_id, tool\_call\_count, event\_count |
| `composio_org_usage_by_project` | `POST /org/usage/tool_calls` | project\_id, tool\_call\_count, event\_count |

***

## 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_credentials` and 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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.