Getting started

Connect a provider

DunOps connects to cloud platforms, deployment services, source control, and domain registrars. Connect one in seconds — your credentials never appear in chat.

How to connect

Open Integrations

Go to Settings → Integrations, or click the plug icon in the left navigation rail. You'll see all available providers grouped by category.

Pick a provider

Browse by category: Cloud, Deploy / PaaS, Source control, or DNS & Registrar. Click any provider card to open its connection panel.

Enter credentials

Paste an API token (most providers) or click Connect with [Provider] for OAuth. DunOps validates the credential immediately and confirms which products are accessible with the supplied token.

Toggle products

Each provider exposes toggleable product groups — for example, Vercel has Deployments and Environment Variables. Turn on the products you need. You can change this at any time without re-entering your credentials.

Warning

Credentials are stored encrypted and never echoed in chat. DunOps reads them from your provider settings at execution time — you never need to paste a token into a message.

API token providers

Most providers use a single Personal Access Token (PAT). Generate one in the provider's dashboard, paste it into DunOps, and you're connected. The token needs read access for discovery and write access for mutations you approve.

Providers that use API tokens include:

Provider	Where to generate	Scope needed
Vercel	Account → Settings → Tokens	Full Account
Netlify	User settings → Applications → Personal access tokens	Full access
Railway	Account → Tokens	Workspace
Heroku	Account settings → API Key	Account-level
DigitalOcean	API → Personal access tokens	Read + Write
Cloudflare	Profile → API Tokens → Create Token	Zone and Account permissions
GitHub	Settings → Developer settings → PATs	repo (read)

Note

Token scope requirements follow the principle of least privilege. DunOps will tell you exactly which scope is missing if a token lacks permissions for an action you attempt.

OAuth providers

Azure and Google Cloud use OAuth — click Connect and sign in with your account. DunOps requests only the scopes it needs. You can revoke access from your provider's authorized apps page at any time.

OAuth connections are per-user, not per-workspace. If another team member needs to trigger actions on the same provider, they connect their own account from their own Settings page.

Azure

Revoke at: portal.azure.com → App registrations → Enterprise apps

Google Cloud

Sign in with Google. DunOps requests Cloud Platform scope. Products (GKE, Cloud Run, BigQuery, etc.) are toggled independently.

Revoke at: myaccount.google.com → Security → Third-party access

Tip

Connect the providers you use most first. You can always add more later from Settings → Integrations.

Next steps

Browse all integrations →

Every provider DunOps supports, grouped by category with a guide to each one.

Key concepts →

How approval gates, plans, and the confirm-before-mutate model work.