Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## Request a toolkit, tool, trigger, or partnership |
| 2 | |
| 3 | The same public request board covers all three request types: |
| 4 | |
| 5 | - a new toolkit or integration; |
| 6 | - a missing tool or action in an existing toolkit; |
| 7 | - a missing trigger or event in an existing toolkit. |
| 8 | |
| 9 | Submit any of these requests at https://request.composio.dev/boards/tool-requests. Include the provider or toolkit, the exact tool/action/API endpoint or trigger/event, and your use case. The request board is the source of truth for status; an ETA is not guaranteed. |
| 10 | |
| 11 | If your company wants its own product added to Composio, apply with a company |
| 12 | work email and product details at https://composio.dev/partnerships#apply. The |
| 13 | public partnership form asks for company, product, and proposed-journey context. |
| 14 | |
| 15 | ## Security, privacy, data-retention, and compliance information |
| 16 | |
| 17 | Use https://trust.composio.dev/ for general security, privacy, data-retention, audit, and compliance information. If the Trust Center does not answer your question, contact Composio support. Use the documented Dashboard self-service path for ordinary organization deletion. Report potential vulnerabilities privately through the security-reporting channels below; direct legal requests, data-erasure requests beyond the self-service flow, and account-specific access questions to Composio support. |
| 18 | |
| 19 | ## Security reporting |
| 20 | |
| 21 | If you believe you have found a potential security vulnerability in Composio, |
| 22 | please report it privately through the channels in our |
| 23 | [security policy](https://github.com/ComposioHQ/composio/security/policy). A |
| 24 | private GitHub Security Advisory is the preferred route, with |
| 25 | `security@composio.dev` available as an email alternative. |
| 26 | |
| 27 | Include enough detail to help the team reproduce and assess the finding, but do |
| 28 | not include customer data, credentials, or other secrets. |
| 29 | |
| 30 | ## Google `access_not_configured` requires a Workspace for Education administrator |
| 31 | |
| 32 | Google documents `400 access_not_configured` as a Workspace for Education app |
| 33 | access-policy error. The institution's Workspace administrator must configure |
| 34 | access for the app; changing Composio scopes or repeatedly reconnecting does not |
| 35 | resolve that policy decision. |
| 36 | |
| 37 | If the organization allows users to request access, the user can submit the |
| 38 | request from Google's error page. An administrator with the required Security |
| 39 | settings privilege can review pending requests or configure the exact OAuth |
| 40 | client under **Security → Access and data control → API controls → Manage |
| 41 | App Access**. The administrator should use the access level and organizational |
| 42 | unit appropriate for the institution. Google says policy changes can take up to |
| 43 | 24 hours, though they usually apply sooner. |
| 44 | |
| 45 | Do not generalize this code to every Google Workspace account. Distinguish it |
| 46 | from `admin_policy_enforced`, `access_denied`, and unverified-app errors before |
| 47 | giving instructions. |