Managing integrations
Manage connected tools so agents and workflows have the right capabilities without unnecessary access.
Check connector availability, connection status, and whether the tool maps to a real workflow or agent action.
Choose the tools Studio can use.
Open the catalog, connect only the systems the operation needs, then use them in agents, workflows, or tools with a clear outcome.
Check connector availability, connection status, and whether the tool maps to a real workflow or agent action.
Check connector availability, connection status, and whether the tool maps to a real workflow or agent action.
What the Integrations page controls
The Integrations page controls which external systems Studio can use. If nothing is connected yet, the main action is Add Integration, which opens the connector catalog.
Use this page as an access checkpoint before assigning a tool to an agent, playbook, or workflow node.
Connector catalog examples
Productivity connectors such as Gmail, Google Calendar, Google Docs, Google Sheets, Google Drive, and Google Meet help agents and workflows draft, schedule, retrieve, or update work.
Sales and support connectors such as Apollo, HubSpot, Freshdesk, Attio, Airtable, and Asana give workflows a way to enrich, route, or update external operating systems.
Minimum access principle
Each integration should grant only what the operating path needs. A workflow that sends a notification should not get unnecessary read access to unrelated data.
If a tool requires broad permissions, make the dependency explicit in the workflow documentation and keep the workflow small enough to audit.
Where integrations show up later
In Agent Builder, integrations can become tools an agent may use. In Playbooks, they can be selected as allowed tools. In Workflow Builder, they can appear through API Call, Outgoing Webhook, Send Message, or other action nodes.
When something fails, debug from the workflow or agent run back to the integration: connection state, permissions, mapped fields, request payload, external response, and fallback path.
Credential and ownership hygiene
Review connected tools when a workflow changes owner, changes purpose, or stops running. Remove integrations that no active workflow or agent uses.
Rotate credentials according to your security policy, and avoid hardcoding secrets inside workflow copy or example payloads.
FAQs
What should I manage here?
The connection state of external tools: which tool is available, who owns it, what permissions it grants, and which workflows or agents depend on it.
Should I connect tools before building the workflow?
Only when the workflow needs the tool. Define the action first, then connect the integration that supports that action.
When should I connect an integration?
Connect an integration when an agent or workflow has a clear need to read context, send a message, update a system, or trigger an external action. Avoid connecting tools without a defined operating path.
How do integrations affect workflow reliability?
Integrations introduce permissions, API responses, rate limits, and failure modes. Use logs, payload mapping, and fallback routing so a failed external action does not become invisible.
Who should manage integration access?
Workspace owners or operators responsible for the workflow should manage access. The person connecting the tool should understand what the workflow can read, write, and trigger.
How do I debug an integration failure?
Check whether the account is connected, the workflow node has the right action, required fields are mapped, credentials are valid, and the external system returned an error.