Connect integrations
Open the Studio Integrations catalog and choose the toolkits agents and workflows can use.

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.
Summary
Open the Studio Integrations catalog and choose the toolkits agents and workflows can use.
Concepts covered
Step breakdown
- Open IntegrationsStart in Studio Integrations to see connected toolkits and available connectors.
- Review connection stateCheck whether the workspace already has connected integrations.
- Open the connector catalogUse Add Integration to browse tools agents and workflows can use.
- Choose relevant toolsSelect connectors based on the agent action or workflow requirement.
What Integrations is for
Integrations is the place where Studio gets permission to use external tools. Connect a tool only when an agent or workflow needs it for a specific job.
Common jobs include sending email, checking calendar availability, updating a CRM, reading a spreadsheet, calling a support tool, or using an internal API through a workflow node.
Use the connector catalog
Click Add Integration to open the catalog. The catalog shows available connectors such as Gmail, Google Calendar, Google Drive, Google Sheets, Airtable, Apollo, Asana, HubSpot, Freshdesk, Slack, and other tools.
Search by the system you need, then choose based on the action the workflow must perform. Do not start from the connector list; start from the operating need.
Connect tools to a real workflow
A sales workflow might use Gmail to draft or send follow-up, Google Calendar to check availability, HubSpot or Salesforce-style CRM tools to enrich account context, and Slack to notify an owner.
A support workflow might use Freshdesk or another helpdesk, a CRM Ticket record, and a channel message. A data workflow might use Google Sheets, Airtable, or an internal API.
Before connecting
Confirm who owns the external account, which workspace should use it, what data Frontline may read, what actions Frontline may take, and which workflow or agent depends on it.
If a connector requires broad permissions, document the reason before enabling it. If the workflow only needs one action, prefer the narrowest scope the connector supports.
How to troubleshoot
If a workflow node fails after you connect a tool, check the connection state first, then the node action, required fields, payload mapping, account permissions, and the external system response in Logs.
If the tool is connected but an agent cannot use it, verify that the agent or playbook has that tool selected. Connection alone does not mean every agent should have access.
Transcript
Open searchable transcript
FAQs
Why connect integrations to Frontline Studio?
Integrations give agents and workflows access to external tools so they can read context or take action across the stack.
Should every workflow use integrations?
No. Use integrations only when the workflow needs an external tool, data source, or 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.