Integration tools are pre-built connectors for actions such as sending an email, creating a support ticket, or looking up an order. Choose a connector below to see its connection requirements, supported actions, and examples.
Run independently through code
You can also execute a saved function, API tool, connected MCP tool, or integration action without running an agent conversation. This uses draft resources and can perform real actions in the connected service. See Run tools without a conversation (Developers) for schema discovery, inputs, permissions, and results.
Start with one action
Follow the Gmail integration walkthrough to collect an email address and send a conversation summary. Then use the Gmail reference to look up its inputs and result.
Setting up an integration
Connect to the provider
You can add, or connect an integration tool directly from within a playbook.

You can also add integration tools from within a workflow using the Integration step, or from the tools CMS tab. Integrations can be managed centrally in Settings → Integrations. Once a tool exists, you can reference it directly in your instructions.
Authenticate
Follow the OAuth flow or enter API credentials to connect your account. Each integration has its own authentication method.
Select tools
Choose which actions you want your agent to have access to. You don’t need to enable everything - only add what’s relevant to your use case.
Using integration tools
There are two ways to use an integration tool:
In a playbook
Add an integration tool to a playbook’s Tools editor. The agent will call it autonomously when it determines they’re needed based on the conversation context, the tool’s description, and your playbook instructions.

Give your tool a clear name and description - together they tell your AI agent what the tool does and when to use it. For extra guidance on when to call it, add that to your instructions.
In a workflow
Drag an integration step onto the canvas and select the specific tool you want to run. Input variables are mapped explicitly in the step config - the agent doesn’t decide whether to call it, the workflow executes it at that point in the flow every time.
Use this when the action is part of a fixed process - for example, always creating a Salesforce case after collecting a complaint, or always sending a confirmation email through Gmail after a booking is made.

Available integrations
Connect another service
Use an API tool when you need to call an HTTP API, or an MCP tool to connect tools from an MCP server. For fixed workflow execution, see the Integration step.