Integrations

Vercel

Dun can redeploy, roll back, read logs, and manage environment variables on your Vercel projects — from chat or a playbook.

Connect with an API tokenHosting3 products

Note

Every mutating action — a deploy, a scale, a secret rotation, a DNS change — surfaces a plan in chat first. Dun never touches your Vercel resources until you approve it.

How to connect

Connect once from Integrations → Vercel, then toggle on the products you want Dun to manage.

Step 1

Open Vercel → Account Settings → Tokens.

Step 2

Create a token scoped to the team that owns the project.

Step 3

Paste the token below and click Connect.

Where to get credentials: https://vercel.com/account/tokens

What Dun can do

Each product below is something you can turn on. The examples are real prompts you can type in a chat thread.

Deployments

Trigger, inspect, and roll back deployments on the projects DunOps reads.

Type in a chat thread

Redeploy my storefront on Vercel
Roll back the last production deploy on example.com
Is my latest Vercel deployment live?

In a playbook, bind vercel.create-deployment to run this as a step.

Permission	Required	What it does
List projects	Yes	Discover which Vercel projects exist on this team.
Read deployment history	Yes	List recent deployments + their build status.
Stream build logs	Optional	Surface build failures in the activity feed.
Trigger approved deploys	Yes	Every deploy is gated by a chat approval; nothing ships silently.

Domains

Attach approved domains to Vercel projects and verify reachability post-cutover.

Type in a chat thread

Show me my Vercel domains

Permission	Required	What it does
Read attached domains	Yes	List which domains are already attached to each project.
Attach approved domains	Yes	DNS changes still go through your registrar.
Verify domain readiness	Optional	Post-cutover health probes so Dun can confirm the swap landed.

Environment variables

Read and propose changes to project env vars — every change confirmed in chat.

Type in a chat thread

Set STRIPE_KEY on my Vercel project's production environment
What env vars does my api project have?

In a playbook, bind vercel.env-var to run this as a step.

Permission	Required	What it does
Read env-var names	Yes	Values stay hidden by default; revealing a value is audited.
Reveal env-var values on request	Optional	Each reveal is a separate audit row.
Apply approved env-var changes	Yes	Adds / updates / removes are gated by chat approval. No silent writes.

Next steps

Browse all integrations →

See every provider Dun can connect to, grouped by category.

Key concepts →

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