Composio

Execute a tool using the composio api.

Search for tools across toolkits for specific use cases. use this when unsure what tool to use or to discover new tools.

Check if any active connected accounts exist for a given toolkit or status of the connected account with a specific id. if an active connected account exists, the tool will return true, otherwise it will return false. active connected accounts allow an agent to perform any actions on top of the toolkit.

Download a file from a public s3 (or r2) url to a local path.

Enable a specific trigger for the authenticated user.

This action retrieves the necessary parameters required to initiate a connection with a specified toolkit. for instance, linear may need 'client id' and 'client secret', zendesk might require similar oauth credentials, and slack could need a 'webhook url'. the required parameters vary based on the authentication scheme employed. for example, api key authentication requires an api key, whereas oauth2 with composio-managed auth typically does not require any parameters because it involves redirecting the user to the toolkit's website for authorization.

Retrieves the response schema for a specified composio tool. this action fetches the complete response schema definition for any valid composio tool, returning it as a dictionary that describes the expected response structure.

Initiate a connection to a toolkit with comprehensive authentication support. supports all authentication scenarios: 1. composio default oauth (no parameters needed) 2. custom oauth (user's client id/client secret) 3. api key/bearer token authentication 4. basic auth (username/password) 5. hybrid scenarios (oauth + connection fields like site name) 6. connection-only fields (subdomain, api key at connection level) 7. no authentication required automatically detects and validates auth config vs connection fields, provides helpful error messages for missing parameters.

List all the available toolkits on composio with filtering options.

List available triggers and their configuration schemas.

Toolkits are like github, linear, gmail, etc. tools are like send email, create issue, etc programmatic functions that can be used to perform the action. not all toolkits support all tools. some toolkits support only a subset of tools that might be possible to perform with that toolkit. use this action to retrieve the toolkits that can be used to perform the action. this list is only probabilistic. retrieve toolkits for a specified usecase. so for example, if use case is to "send an email" this action will return all the toolkits that can be used to send email. simiarly if use case is to "create a github issue" this action will return all the toolkits that can be used to create a github issue. after using this, to confirm whether the toolkit can indeed potentially support the use case, use the action retrieve actions.

Toolkits are like github, linear, gmail, etc. tools are like send email, create issue, etc programmatic functions that can be used to perform the action. get tools for a given usecase using similarity search. these tools are most relevant to the usecase but still might not be actual tools needed for the usecase. this decision should be made by you. this should be used to narrow down for a toolkit, and find the most relevant tools for the usecase. in some cases, you might want to even check if the usecase is supported by the toolkit or not.

Wait for a connection to be established for a given toolkit or check the status of a connected account with a specific id. wait for a given amount of time and then check again the status of the connection.