Skip to content

Get started

Connecting an integration

How to connect any provider — who can do it, the three flow shapes, and how to tell it worked.

Integrations let Dave read from, and act on, the systems you already run. For the specifics of one provider, see its page under Integrations.

You need the Manage integrations permission, held by the Owner, Infra Owner and Service Infra Owner roles. Developer can view connections but not add, reconnect or disconnect them.

  1. Open Integrations. A new workspace reads Nothing connected yet.

  2. Choose Add integration. The catalog groups providers by Source Code, Cloud, Communication, Workflow, Knowledge, Monitoring and Compliance.

  3. Pick a provider and complete its flow — see The three flow shapes.

  4. Confirm the connection reads Active. Until it does, the flow is not finished.

  5. Choose Run health check. Active means “set up correctly”, not “working right now” — a connection can be Active and still fail, usually because the credential was revoked afterwards. The list shows an N failing pill for that.

Approve the access in the provider’s popup and it closes itself.

Asana · Confluence · GitHub · GitLab · Jira · Linear · monday.com · Notion · Sentry · Slack

If the popup is blocked, the connection row keeps an Open the setup page action — nothing is lost.

Azure DevOps asks for your organization name first, then sends you to Microsoft. Bitbucket asks for your workspace first, then sends you to Bitbucket.

These collect credentials or identifiers, then wait on your side. The connection sits at Setup incomplete meanwhile.

Provider What finishes it
AWS Deploying a CloudFormation stack
Backblaze B2 Nothing — Dave validates the keys
Google Cloud Running a Cloud Shell setup command
Kubernetes Installing the Dave agent with Helm
Microsoft Azure Nothing — Dave validates the credentials
Claude Platform Creating federation rules in the Claude Console
Cloudflare Nothing — Dave validates the token
Coralogix Nothing — Dave validates the keys
Datadog (API) Nothing — Dave validates the keys
Modal Nothing — Dave validates the tokens
Nebius Running a Cloud Shell setup command
Neon Nothing — Dave validates the key
OpenAI Nothing — Dave validates the keys
PagerDuty Nothing — Dave validates the key
Vanta Nothing — Dave validates the credentials

Most form-based providers also ask for a Label — the name you use to refer to the connection in conversation, as in “use prod to list S3 buckets”. Labels are unique per workspace, up to 64 characters: letters, numbers, spaces, underscore and hyphen. Kubernetes calls it Cluster name.

Badge Meaning What to do
Active Set up correctly and usable. Nothing.
Setup incomplete Started but never finished — nothing is connected yet. Resume setup, or Delete to start over.
Error The connection broke. The row carries the reason. Fix it at the provider, then Connect again.
Disconnecting Teardown started; provider-side resources are still being removed. Finish any cleanup the provider needs.
Disconnected Fully removed. Grouped separately in the list. Nothing.

Connections are sorted worst-first, so anything needing attention floats to the top.

While a provider is being validated, Dave checks about ten times over two minutes. If the setup isn’t finished by then, finish it on the provider side and choose Check connection.

Providers you connect through a form can be connected more than once. Once one is connected, the button reads Add (noun):

Unit Providers
Account AWS, Backblaze B2, Cloudflare, PagerDuty, Vanta
Workspace Bitbucket, Google Workspace, Modal
Organization Azure DevOps, Claude Platform, Datadog (API), Neon, OpenAI
Project Google Cloud
Subscription Microsoft Azure
Cluster Kubernetes
Team Coralogix

Every other provider — including all request providers (Asana, Jira, Linear, monday.com, Notion) — connects once per workspace.

Symptom Fix
Popup was blocked Use Open the setup page on the connection row.
Stuck at Setup incomplete Resume setup, or Delete to discard and start over.
Gave up waiting for the provider Confirm you ran the setup step, then Resume setup. Scripts re-run safely.
Health check fails on Active Usually a revoked or expired credential — Connect again to re-authorize.
Shows Error Read the reason on the row, fix it at the provider, then Connect again.

Two providers need more than Connect again: Microsoft Azure needs a fresh client secret first, and Kubernetes has no credential to re-authorize — fix the agent, or disconnect and reinstall.