Connect Vercel

What it pulls

Projects and the last 30 days of deployments: production deployment frequency (per week), change-failure rate (failed vs. successful production deploys), and average build duration. Vercel exposes no commit timestamp, so commit→prod lead time is omitted (not faked), and it has no vulnerability-scan API, so Security Readiness is not fed.

The exact fields the connect form asks for — and where to find each value.

Access token

vercel.com/account/tokens → Create Token → scope it to the right Team and set a short expiration. Vercel has no read-only token tier, so treat this as sensitive — the connector only ever issues read (GET) requests.

Team ID or slug (optional)

Leave blank for a personal account. For a Team, copy the Team ID from vercel.com/<team>/settings (or use the slug) so deployments + projects resolve to that team.

1. 1

   Create an access token

   Open the link above (vercel.com/account/tokens) → Create Token. Name it “ShipReady Metrics”, scope it to the relevant Team (or your account), and set a short expiration.

2. 2

   Copy the token

   Copy the token value now — Vercel shows it only once.

3. 3

   Find your Team ID (Teams only)

   For a personal account, skip this. For a Team, copy the Team ID from vercel.com/<team>/settings (or use the team slug) so projects and deployments resolve to that team.

4. 4

   Paste the token and connect

   Enter the token in Access token (and the Team ID/slug if applicable) and click Connect. We validate it live, encrypt it at rest, and run the first sync.

Troubleshooting

Token rejected (401/403).

Recreate the token at vercel.com/account/tokens and make sure it is scoped to the Team that owns the projects. For a Team, set the Team ID or slug field — without it the token resolves to your personal scope and sees no team deployments.

Connected, but deployment frequency shows “not measured”.

The connector only counts deployments whose target is production in the last 30 days. If you deploy only previews (or the token can't see the team), there are no production deploys to rate — set the Team ID/slug and confirm production deployments exist.