Skip to content
Groundcrew
Get started
Docs menu

Connect Vercel

Groundcrew reads your Vercel projects with a token you create and paste. It only ever calls Vercel's read endpoints, and it never asks Vercel to decrypt a value.

Before you start

  • You are an owner of the Groundcrew workspace.
  • You are a member of the Vercel team whose projects Groundcrew should read, or it is your personal account.
  • For the map to show which repository each project deploys from, connect GitHub too.

Create a token and connect

  1. Create the token

    On vercel.com, open Account Settings, then Tokens (vercel.com/account/tokens). Create a token with your team as its scope, not your whole account, and an expiry date you are comfortable with.

  2. Find the Team ID

    In the team's Settings, General, copy the Team ID. It starts with team_. For a personal account, leave it empty.

  3. Connect

    In Groundcrew, open Connections and choose Add token on the Vercel card. Paste the token and the Team ID and choose Connect. Groundcrew checks the token can read the team before it saves anything. Then run discovery.

The token is encrypted before it is stored and is never shown again.

What Groundcrew reads

  • Projects and the Git repository each one is linked to.
  • Production domains and recent production deployments.
  • Env var names and types. Values are not kept, with one exception: a plain variable (not encrypted, sensitive, or secret) whose name ends in _URL or _HOST. That value shows which backend a frontend calls, so the map can draw the line between them.
Safety:

Groundcrew only calls a fixed list of Vercel read endpoints and refuses any other path. It never uses Vercel's decrypt option, so encrypted and sensitive values stay unreadable to it.

How Vercel shows on the map

Each project and its latest production deployment appear on the map. A project linked to a repository gets a line to it, and a project whose API_URL-style variable points at one of your AWS or Kubernetes services gets a calls line to that service. When that backend has an incident, Medic follows the line and reads the frontend's recent deployments as evidence too.

Troubleshooting

  • Vercel returned 403. The token's scope does not include the team you entered. Create a token scoped to that team, or check the Team ID.
  • Vercel returned 401 or 404. The token expired or was deleted, or the Team ID is wrong. Create a new token and connect again.
  • No projects on the map. The Team ID was left empty, so Groundcrew read your personal account. Remove the connection and add it again with the Team ID.
  • A project has no line to its backend. Its variable is encrypted or sensitive, or its name does not end in _URL or _HOST. That is expected: Groundcrew does not read protected values.

Change or remove

When a token expires, the connection shows an error. Remove the connection and add it again with a new token.

To disconnect, remove the Vercel connection on the Connections page, which deletes everything Groundcrew discovered through it, then delete the token in your Vercel account settings.