Tools

The pages in this section describe the external integrations that can be offered to SquadOS agents. Each reference identifies the service, known authentication methods, and the actions published in the documented snapshot.

The catalog is not a list of tools automatically available to every agent. There are two independent configuration layers:

1. the organization activates the integration, connects an account, and may restrict its actions;
2. each agent receives an account and a subset of the allowed actions.

Activating an integration does not add it to agents. Connecting an account also does not authorize any agent until the tool is added and the agent is saved.

Before choosing an integration

Define the expected result and the least access required. Confirm:

• which external service holds or will receive the data;
• which account or workspace must be used;
• whether the operation only reads data or also creates, changes, or deletes it;
• which exact actions the agent needs;
• which conversation data may be sent to the third-party service.

Do not choose an integration only because the service name seems appropriate. Read the action list and its parameters: they determine what the agent can actually do.

Make an integration available to the organization

The Tools route (/admin/tools) requires View tools. Activating, connecting, and editing actions requires Create and edit tools; removal belongs to Delete tools.

1. Open Tools and select Available.
2. Find the integration and open its card under Configure tool.
3. Select Activate. The integration moves to Active.
4. Open the active integration and select Connect now.
5. If more than one method is available, choose the appropriate authentication method.
6. Complete the flow hosted by Composio. Tools without authentication connect directly.
7. Under Accounts, confirm that the account is active.

Activation and authentication are separate steps. An integration can be active for the organization while still appearing under Disconnected or Awaiting authentication. See the complete flow in Organization Tools.

Credentials and accounts

OAuth, API keys, bearer tokens, basic authentication, and service-specific fields go through the secure page hosted by Composio. Never write passwords, tokens, or keys in the agent prompt, tool description, or a knowledge base.

An integration can have several accounts. Use names that distinguish their purpose and environment, such as Support — production and Marketing — staging. To recover a credential, use Accounts → Account actions → Reconnect on the correct row so the account identity and assignments are preserved.

If a reference in this section explains how to obtain a key or OAuth credential, follow that preparation only when the authentication method selected in the connection flow asks for those values. Platform-managed OAuth does not require each organization to create its own provider application.

Restrict organization actions

Open an active integration and use Edit actions to define the maximum set available to the organization. Without a curated list, every action published by the integration is available for agent selection.

Prefer the smallest possible set. Separate read actions from actions that send messages, create records, move money, or delete content. An action run by an agent uses the permissions of the connected account in the external service.

Add it to an agent

1. Open the agent and go to Tools.
2. Select Add Tool.
3. Choose an active organization integration.
4. Choose the correct account and only the required actions.
5. Review configurable parameters, save the agent, and run a safe test.

The agent picker shows only active integrations that have not already been added to that agent. The agent’s action list can never exceed the organization’s curation.

How to read each reference

Each integration page contains:

• Overview: the service purpose and typical uses;
• Authentication: methods known to the snapshot;
• How to connect: provider-specific preparation and the SquadOS entry point;
• Available actions: technical identifier, inputs, requirement, and output.

Copy identifiers and parameters exactly; do not invent an action or field. The Composio catalog evolves, so treat the version and date in frontmatter as the snapshot for that page. If the agent editor or the schema delivered at runtime differs, use the product’s current contract and flag the documentation for review.

Catalog by category

The documented catalog contains 106 integrations:

Category	Integrations
AI & Models	12
Web Scraping & Search	7
Analytics & BI	8
Email	8
CRM & Payments	7
Communication & Chat	7
Productivity & Management	12
Google Workspace & Files	5
Dev & Infra	22
Marketing & Social	8
Media & Design	7
Collaboration & Other	3

Use the sidebar to open each integration reference. The presence of a page documents the connector, but does not guarantee that it is enabled for the plan, platform, or current organization.

Quick troubleshooting

• Missing from Available: the integration may not be enabled on the platform or may already be under Active.
• Awaiting setup: a superadmin must still prepare platform authentication.
• Awaiting authentication: open the integration and complete Connect now.
• Missing from the agent: confirm that the integration is active, its account is connected, and it has not already been added to that agent.
• Action is missing: review Edit actions for the organization and the agent’s selection.
• Parameter is rejected: use the current schema shown by the product; do not adapt its name or type by trial and error.
• Account is in error: reconnect from its own row under Accounts.

The product has known permission limitations in this area. Until they are fixed, grant View tools only to people authorized to manage integrations and review the cautions in Organization Tools.