Vercel setup guide

Agents work with your code, deployments and incidents.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Vercel, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Access token

API key.

1. With your personal account selected in the dashboard's scope selector, open Account Tokens (https://vercel.com/account/tokens) and enter a name such as "Everdeck".
2. Under Scope pick your team with All Projects. (Full Account also works, but then paste the Team ID into the form too. A token for a single project is refused for team-level requests, which several actions make, so it is not recommended.) Your team may require two-factor authentication or SAML before you can create tokens for it.
3. Choose an expiration, select Create, and copy the token (it starts with vcp_ and is shown once) into the form.
4. You don't need to add a webhook: live updates from Vercel (deployment events and anomaly alerts) aren't available yet, so leave both webhook secrets empty.

Field	What to enter
Access token	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.
Team ID (only for a Full Account token) (optional)	Text. For example team_.... Shown in your team's settings. Team and project tokens do not need it.
Webhook secret (optional, not used yet)	A secret: Everdeck saves it encrypted and never shows it again. Live updates from Vercel aren't available yet; leave this empty.
Alerts webhook secret (optional, not used yet)	A secret: Everdeck saves it encrypted and never shows it again. Vercel alerts can't reach agents yet; leave this empty.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Vercel until you delete or rotate it there.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List projectsTier 0 · ReadReads outside contentvercel_list_projects

  List projects with id, name, framework, connected Git repository and production branch, most recently updated first.

• Read a projectTier 0 · ReadReads outside contentvercel_get_project

  Read one project by id or name: framework, Node.js version, root directory, connected repository and production branch, and the current production deployment.

• List deploymentsTier 0 · ReadReads outside contentvercel_list_deployments

  List deployments, newest first, with id, URL, state (BUILDING, ERROR, INITIALIZING, QUEUED, READY, CANCELED or BLOCKED), target (production or preview), creator, Git metadata (branch, commit message and SHA) and whether each can be rolled back to.

• Read a deploymentTier 0 · ReadReads outside contentvercel_get_deployment

  Read one deployment by id (dpl_...) or hostname: state, why it failed (error code, message and step), target, aliases, Git source, creator and timings.

• Read build logsTier 0 · ReadReads outside contentvercel_get_build_logs

  Read a deployment's build output (commands, stdout and stderr), newest lines first by default, to find why a build failed.

• Read runtime logsTier 0 · ReadReads outside contentvercel_get_runtime_logs

  Follow a deployment's runtime logs live (function, middleware and request logs) for up to max_seconds or max_lines: time, level, request method, path and status, and the message, newest first. Only logs written while it runs are returned; earlier logs are not (the Vercel dashboard's Logs tab has them, and get_build_logs reads a build's logs).

• List environment variable namesTier 0 · ReadReads outside contentvercel_list_env_vars

  List a project's environment variables by name with their targets (production, preview, development), type and last change. Values are never returned.

• List a project's domainsTier 0 · ReadReads outside contentvercel_list_project_domains

  List the domains attached to a project with verification status (and the DNS record still needed when unverified), redirects and the Git branch they follow.

• RedeployTier 3 · ExternalReads outside contentvercel_redeploy

  Build an existing deployment again with the same settings and environment variables (or the branch's latest commit when withLatestCommit is true). Send target production to rebuild the live site: the new build goes live for visitors once it is ready. Without a target Vercel makes a preview deployment, even when the original was a production one.

• Promote to productionTier 3 · ExternalReads outside contentvercel_promote_deployment

  Point production traffic (the production domains) at an existing deployment without rebuilding it. Also undoes a rollback and switches automatic production deploys back on.

• Roll back productionTier 3 · ExternalReads outside contentvercel_rollback_deployment

  Instantly point production back to an earlier production deployment (one with isRollbackCandidate true). Afterwards new pushes do not go live automatically until a deployment is promoted. Hobby plans can only roll back to the immediately previous one.

• Cancel a deploymentTier 2 · Reversiblevercel_cancel_deployment

  Stop a deployment that is still queued or building. Fails if it is already READY, ERROR or CANCELED.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Vercel later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit.

To stop agents using Vercel, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.