Crowswatch
Vercel

Stack Monitors

Monitor Vercel Deployments with Crowswatch

Monitor deployments, build performance, domains, SSL certificates, web analytics and firewall security across your Vercel projects directly from Crowswatch.

What This Integration Provides

  • Deployments: live deployment state, build durations, success rates and failures
  • Projects: framework, linked repository, production aliases and latest deployment state
  • Domains & SSL: custom domain verification, nameserver checks, registration expiry and certificate expiry with auto renew state
  • Web Analytics: page views and visitors per project, plus top pages, referrers and countries
  • Firewall security: active attack anomalies, denied and challenged traffic, and each project's WAF posture (custom rules, OWASP Core Ruleset, bot protection)
  • Account activity: the audit stream of deployments, domain and team changes

Requirements

RequirementDetail
Vercel accountHobby or above
Access tokenPersonal access token from account settings
Team IDRequired if your projects are under a Vercel team
Estimated setup time~5 minutes

Step 1: Generate Credentials

Vercel uses personal access tokens for API authentication.

To create an access token:

  1. Log in to vercel.com
  2. Click your profile avatar → Settings
  3. In your Personal Account settings (not a team's settings), go to Tokens
  4. Click Create
  5. Enter a name (e.g. crowswatch-monitor)
  6. Select the Scope: choose Full Account to monitor all teams, or select a specific team to limit access
  7. Set an optional expiration date
  8. Click Create Token
  9. Copy the token, as it is only shown once
Vercel access tokens do not currently offer per-permission read/write controls. Use team-scoped tokens rather than full account tokens where possible to reduce blast radius.

Step 2: Locate Required IDs

Team ID (required for team projects)

  1. Open your team dashboard on Vercel
  2. Go to the team's Settings → General
  3. The Team ID is listed in the General section
  4. It is also visible in the URL: vercel.com/teams/<team-id>/settings

If all your projects are under your personal account and not a team, you do not need a Team ID.

Step 3: Add Credentials to Crowswatch

Navigate to: Crowswatch → Add Service → Vercel

FieldValue
Access TokenThe token generated in Step 1
Team IDYour Vercel Team ID (if applicable)

Available Metrics

Deployments

  • Deployment state (ready, error, building, cancelled)
  • Build durations: average, median and slowest, per project
  • Success and failure counts for the selected period

Projects

  • Framework, Node version and linked repository
  • Latest deployment state and production aliases
  • Cron jobs, deployment protection and Speed Insights state

Domains & SSL Certificates

  • Custom domain verification and nameserver configuration
  • Vercel’s own check that each domain is pointing at Vercel
  • Registration expiry and TLS certificate expiry with auto renew state

Web Analytics

  • Page views and visitors per project
  • Top pages, referrers and countries per project

Security

  • Active DDoS / attack anomalies from the Vercel Firewall
  • Denied and challenged traffic with host and volume
  • WAF posture per project: custom rules, IP rules, OWASP Core Ruleset, bot protection and AI bot handling

Account

  • Audit stream of deployments, domain, alias and team changes

Coming soon

  • Serverless function invocations, duration and errors (no public Vercel API yet)
  • Bandwidth and usage by project (no public Vercel API yet)

Connect

  1. Enter your Access Token and, if applicable, your Team ID
  2. Click Verify to confirm the credentials are valid
  3. Select the projects and metrics you want to track
  4. Click Connect

Security

  • Use a team-scoped token rather than a full account token where possible
  • Set an expiration date on the token and rotate it periodically
  • Create a dedicated token for Crowswatch rather than sharing with other systems

Troubleshooting

Authentication error

Verify the token has not expired. Confirm the token was created under your Personal Account settings, not a team's settings.

Team projects not visible

Ensure the token scope includes the relevant team. Confirm the Team ID is correct by copying it directly from the team settings page.

Deployment data not appearing

The Vercel API only returns deployments for projects the token has access to. If using a team-scoped token, ensure the projects are under that team.