Connect Apps

Connected apps let an agent work with external services through supported integration flows. Use native provider connections when offered, or configure an external MCP server or governed API integration. Available providers and controls depend on the deployment.

When to connect an app

Connect an app when the agent's job requires direct access to a system, such as a messaging channel, task system, spreadsheet, CRM, or other SaaS tool.

Do not connect an app only because it might be useful later. Each connection increases the agent's available surface area.

Typical setup

1. Select the intended personal, Organization, or Team workspace, then open the agent.
2. Find the tools, apps, or integrations area.
3. Search for the app.
4. Connect or authorize the app when prompted.
5. Enable or assign the app where its setup flow requires it, and select the files, channels, or other resources the agent needs. Some managed connections are inherited within their workspace.
6. Send a test instruction in chat.
7. Review the timeline for tool activity or pending requests.

Agent setup guidance links to the applicable native connection or integration settings. New-agent app review shows setup requirements; it does not preselect an external app catalog.

For spreadsheet workflows, see Google Sheets.

For Discord channel workflows, see Discord.

For lead sourcing and enrichment workflows, see Apollo.

For CRM workflows, see HubSpot.

App channels and triggers

Some connected app flows can act like inbound channels. For example, an app event can trigger the platform to respond to a message or event.

Connecting an account and subscribing an agent to inbound events are separate steps. Configure the provider-specific channel, file, or event selections shown in the UI, then verify a real event. See Discord for channel subscriptions and Email Settings for mailbox receiving controls.

Safety checklist

• Check whether access is per-agent or inherited by agents in the workspace before connecting a shared account.
• Prefer read-only scopes when the app supports them and the workflow allows it.
• Ask the platform to summarize what it will do before external writes.
• Configure available enforced approval controls for sensitive actions. A prompt asking for approval does not create a mandatory gate for every app operation; see Instructions Versus Enforced Controls.
• Remove app connections that are no longer needed.

Verify scope and reconnect

Confirm the provider account and workspace after authorization. A connection does not grant access to files, channels, or records the provider account cannot access. Some providers require a file selection, bot installation, or per-agent subscription in addition to sign-in.

If access expires or is revoked, reconnect through the same app control, review scopes, and try a small read against a known record. Check the agent's assignment before repeating the original work. Disconnecting prevents future authorized use of that connection; it does not reverse actions already completed in the provider.

For an API without a suitable app connection, Organization administrators can use API spec integrations or MCP servers.

Developer note

Use native Webhooks And Events for inbound agent triggers and outbound delivery. Embedded Pipedream connection and trigger routes have been removed. External MCP services are configured through ordinary MCP server settings; no provider-specific setup or compatibility is supplied.