Integration
Vercel
Deployment status monitoring and environment variable parity checks.
Most launch incidents are not "the code is wrong"—they are "the deploy that shipped is not the deploy you think is live." PreFlight gives visibility into deployment state, production domains, and release-window drift so a bad promotion is caught before customers hit it.
Requirements
<IntegrationRequirements
items={[
"Vercel API token with read access to the team or personal scope that owns the project",
"Vercel project ID or project name to watch",
"Production domain(s) that should resolve to the latest healthy deployment",
"Optional deploy webhook secret for real-time Vercel Watch events",
]}
/>
Use a read-scoped token dedicated to PreFlight. The integration never needs write access to trigger or roll back deployments—it observes and reports.
What PreFlight checks
| Probe | What it proves |
| --- | --- |
| Token reachability | The API token authenticates and can list the connected project. |
| Production deployment | The latest production deployment exists and is in `READY` state. |
| Domain sweep | Each configured production domain resolves to the expected deployment. |
| Deploy anomaly timeline | Failed builds, alias changes, and promotions are recorded for drift detection. |
| Ghost domain sweep | Stale or unassigned domains that could steal traffic are flagged. |
Vercel Watch runs continuously, outside a manual check or the 24-hour Monitoring window. Turn it on when you promote frequently, when DNS could point at the wrong deployment, or when you want deploy and domain anomalies in Incidents and the Event Timeline automatically.
Failure guidance
| Symptom | Fix |
| --- | --- |
| Token rejected | Regenerate the token in Vercel account settings with access to the owning team. |
| Deployment not `READY` | Open Vercel deployment logs, fix the build, and re-promote. |
| Domain points at old deployment | Assign the production alias to the newest healthy deployment and confirm DNS propagation. |
| Anomaly noise after deploy | Expected immediately after promotion; Vercel Watch settles once the alias is stable. |
| Env parity drift | Sync environment variables between Vercel and your PreFlight project settings. |
Dashboard setup
Go to Integrations → Vercel and paste a read-scoped API token.
Enter the Vercel project ID and production domain(s) to monitor.
Optionally configure the deploy webhook secret for Vercel Watch real-time events.
Enable Vercel Watch and run Pre-Flight Check to confirm deployment and domain probes.
<RelatedLinks
links={[
{ href: "/docs/guides/deploy-gates", title: "Release Rules", description: "Block CI when deployment health or Uptime Monitoring samples fail." },
{ href: "/docs/integrations/deployment", title: "Deployment", description: "API latency, uptime, and launch window monitoring." },
{ href: "/docs/integrations/cloudflare", title: "Cloudflare", description: "Zone SSL and security settings that affect live traffic." },
{ href: "/docs/integrations/environment", title: "Environment", description: "Public URL, DNS, and TLS checks on your production domain." },
]}
/>
