Sign Up
Integration agency icon

Agency Domain

Integration Agency

Control how your agent connects services, APIs, and external tools.

The Integration agency governs how your agent connects external services, sets up API integrations, and configures third-party tools. Integrations bridge your workspace with the wider ecosystem, and the right oversight level depends on the sensitivity of the systems being connected.

What Integration Covers

Integration actions include connecting to third-party APIs, configuring webhooks, setting up OAuth connections, linking external services like analytics or monitoring tools, installing packages or plugins, and managing API keys and credentials. When your agent connects your project to a notification service or sets up a CI/CD pipeline, that is an integration action.

Oversight Levels

Silent

Your agent sets up and manages integrations without asking. It connects services, configures APIs, and installs tools as needed to accomplish its work. This can work when your agent operates within a well-defined technology stack and the integrations carry minimal security risk.

For example, your agent might automatically connect a logging service to a new microservice it created, using credentials already available in your workspace.

Report

Your agent sets up integrations and notifies you about what was connected. You get messages like "I've connected the Slack webhook to your deployment pipeline so you'll get notifications when releases ship. Here's the configuration." You can review what was connected and verify the configuration.

Report is a reasonable default for many integration scenarios. It lets your agent handle the technical setup while keeping you aware of what systems are now connected to your workspace.

Approval

Your agent proposes integrations and waits for your permission. You see requests like "The monitoring dashboard needs access to your database metrics. I'd like to set up a read-only connection using these credentials. Should I proceed?" Your agent configures nothing until you approve.

Use this for integrations that involve sensitive data, production systems, or third-party services that will have access to your infrastructure. Any integration that involves sharing credentials or granting access to external systems is worth reviewing before it happens.

When to Use Each Level

Integration reversibility varies. Some integrations are easy to disconnect, while others create dependencies that are harder to unwind. An API connection can usually be revoked, but if other systems have started depending on it, removing it can break things.

The security dimension is the key consideration. Integrations often involve granting access, sharing credentials, or exposing data to external services. A poorly configured integration can create security vulnerabilities or leak data. For this reason, Approval is wise for integrations involving production data or sensitive systems. Report works well for development tools and non-sensitive services. Silent is appropriate for routine, low-risk integrations within your existing technology stack.