Integrations
Integrations connect Polylane to the services around your system. Each one gives agents something concrete to work with, and this page explains connecting and disconnecting once so the provider pages do not have to.
What it does
Connecting a tool registers query tools agents can call: search logs, fetch a pull request diff, run a metrics query, or describe a resource. Connecting a cloud provider also syncs its resources into the topology, where scheduled checks and impact assessments use them.
How connecting works
Every provider has a guided connect flow in the console under Settings > Integrations, with cloud providers under Settings > Clouds. The method depends on the provider, and credentials are stored encrypted.
| Method | Description | Examples |
|---|---|---|
| API key or token | You paste a key created in the provider's console. | Datadog, Cloudflare, Linear |
| OAuth | You sign in to the provider in the browser and grant access. | Sentry, Slack, Vercel |
| App install | You install the Polylane app on your organization and pick what it can read. | GitHub |
| CloudFormation | You deploy a stack that creates a read-only role in your account. | AWS |
| Helm | You install an agent in the cluster. | Kubernetes |
Each provider has its own page with setup steps, permissions and troubleshooting at /integrations/<type>, for example /integrations/cloudflare. Providers that connect without a browser also carry a Pipeline tab there, with the exact API calls for a CI job. From the terminal, polylane cloud connect and polylane integration connect run the same flows.
How disconnecting works
Disconnect from Settings > Integrations, from the cloud account page, or with polylane integration disconnect and polylane cloud disconnect. Disconnecting stops every sync and check, deletes the credentials Polylane held, and removes what Polylane set up on the provider side wherever the provider's API allows it. Each integration page states exactly what is removed and what stays, and what stays is always something only you can remove.
| Provider side | Removed on disconnect | Stays |
|---|---|---|
| AWS | The CloudFormation stack | The IAM role, its policies and the CloudTrail S3 bucket, which the stack keeps on purpose |
| Slack | The bot token, which is revoked | The Slack app installation and the channels Polylane created |
| GitHub | The credentials Polylane held | Autofix branches and pull requests, the onboarding branch, and check runs on past commits |
| Datadog | The webhook Polylane registered | The @webhook-polylane mention and the polylane:managed tag on your monitors |
| Vercel | The credentials Polylane held | The Vercel integration configuration and the polylane-* drains |
Deleting a workspace disconnects everything in it the same way, with one exception: the AWS CloudFormation stack is only deleted when you disconnect the account itself. Disconnect AWS accounts before deleting a workspace, or delete the stack in the AWS console afterwards.
Catalog
Open any integration for its tools, connect guide, and what disconnecting removes.
Git providers
Connect your codebase
Observability
Query metrics, logs, and traces
Code agents
Delegate code changes to autonomous agents
Communication
Collaborate with your team
Knowledge base
Search docs and wikis
Issue tracking
Create and manage issues
Incident management
Declare and respond to incidents
CI / CD
Build, test, and deploy pipelines
Product analytics
Understand user behavior and feature usage
Cloud providers
Connect your infrastructure
Protocols
Bring your own tools via standard protocols
Related
- Clouds for what a connected cloud account gives you and how to read its page.
- Repositories for what connecting GitHub unlocks.
- Work from your tools to connect and manage integrations from your coding agent.