Integrations

Integrations give agents something to work with. Depending on the provider, connecting registers:

• Query tools the agent can call: search logs, fetch a pull request diff, describe a cloud resource, run a metrics query.
• Triggers automations can listen to: github.push, alert, vercel.deployment, slack.message, and platform events like polylane.cloud_account.connected.
• Resources that join the context graph. Cloud providers sync their resources into the topology, where detection and investigation pick them up.

How connecting works

Every provider has a guided connect flow in the console. The method matches the provider: AWS deploys a CloudFormation stack that creates a read-only role, GitHub and Sentry install an app through OAuth, Vercel installs an integration from the Vercel Marketplace, and most others take an API key or token. Credentials are encrypted before they are stored, and the agent never sees them.

You can also connect from the terminal:

polylane cloud connect --provider aws
polylane integration connect --type datadog

Each provider has its own page with setup steps, permissions, and troubleshooting at /integrations/<type>, for example /integrations/cloudflare.

Catalog

Click any integration for its tools, triggers, automation templates, and connect guide.