Integrations Overview
Connect external APIs and services to your agents
Integrations connect your agents to external systems. Each integration groups related tools under a shared configuration and authentication setup.
Sandbox Mode
Every integration can be exercised without touching production. Each integration config carries a sandboxMode setting — vendor sandbox, the Fruxon simulator, or a read-through hybrid that reads from prod and writes to the simulator. Used by evaluation runs, CI, and any agent run you want isolated from live data.
See Sandbox Mode for the full guide.
How Integrations Work
An integration defines:
- Configuration — shared parameters like a base URL that all tools in the integration use
- Authentication — how requests are authorized (API key, OAuth, bearer token, etc.)
- Tools — the individual operations your agents can perform
Integration configs are set up at the tenant level and picked per step in Agent Studio. When an agent executes, it uses the config's credentials to call the attached tools.
Authenticating an integration
Most integrations either use an API key / token pasted at setup time, or run an OAuth flow where the user signs in and grants scopes. Two affordances are common across the catalog:
OAuth scope picker
For OAuth integrations, the setup wizard shows a scope picker — a list of OAuth scopes the integration can request, each with a description of what it unlocks. You grant only the ones the agent actually needs. A tool that requires a scope you didn't grant will fail at execution; reauthorize and add the missing scope, no need to redo the whole config.
Integrations with an explicit scope picker:
- Airtable, ClickUp, Discord, GitHub, Google Ads, HubSpot, Intercom, Jira, Linear, Monday, Notion, Outlook, Reddit, Shopify, Typeform, Zoho CRM.
Connection testing
For credential-based integrations, the saved config exposes a Test action. Clicking it sends a minimal authenticated request to the vendor and reports whether the credentials, base URL, or scopes are valid — before any agent step depends on them. Failed tests print the vendor's error message verbatim.
Integrations with the Test action:
- Confluence, Datadog, Firecrawl, GCP Logging, GitHub, GitLab, Grafana, HubSpot, Intercom, Jira, Linear, Mailchimp, Mercury, Notion, Sentry, Shopify, Slack, Stripe, Supabase, Tavily, Typeform, Zendesk.
System Integrations
Pre-built integrations with ready-to-use tools. Select one, provide your credentials, and start using the tools in your agent.
