Connect Vercel to Saasmetry
Builds and their outcomes, so a failed deploy shows up beside the errors it caused.
What Saasmetry reads
Refreshed every 5 min. Read-only throughout: Saasmetry never writes to Vercel.
Create the credential
- Vercel → Account Settings → Tokens → Create Token.
- Set its scope to the team that owns the projects you want read, and give it the longest expiry you are comfortable with.
- After connecting, pick the project each product reads from its data sources.
Worth knowing
- Vercel issues no read-only token. The token carries your own access, and Saasmetry only ever reads with it.
- A token expires on the date you chose when creating it, and syncing stops dead when it does — Vercel sends no warning.
- Scope the token to one team. A personal token cannot see a team's projects unless the team is named, which is what the optional Team ID field is for.
Is it safe to paste?
A Vercel token carries your access in its selected account or team; Vercel offers no read-only token. Saasmetry encrypts it and only reads project and deployment data.
Vercel issues no read-only key, so this credential is broader than Saasmetry needs. Saasmetry only ever reads — but you should know that before you paste it, rather than after.
Also worth connecting
Connect Vercel in about a minute
Free plan, no card: one product and two integrations.
Start free