Guides
Connect Vercel to Uptimy Cloud
Install the Uptimy integration, pick your projects, and get a monitor for each, incidents for failed production deploys, and an automatic redeploy of the previous version when production goes down. About five minutes.
Overview
Uptimy's Vercel integration reads the projects you give it access to and sets up three things:
- Monitors: an HTTP check for each project's production domain (your custom domain, or
vercel.app), from several regions. Every plan, within its monitor limits. - Deploy events: a failed production deploy opens an incident. Needs a Vercel team on Pro or above.
- Recovery: a workflow that redeploys the previous production version when its monitor goes down, with limits that stop it from looping. Growth and above.
Vercel runs your apps as functions and static files, so there's nowhere to run the open-source Uptimy Agent next to them. Checks come from Uptimy Cloud.
1. Install the integration
New to Uptimy? Create an account and choose Import from Vercel during setup. The new workspace is named after your Vercel team.
In an existing workspace, open Settings → Integrations and choose Vercel.
Vercel asks which team and projects Uptimy can access. Approve it and you come back to Uptimy. There's no token to create or paste.
2. Import your projects
Untick the projects you don't want, adjust each health path and expected status, and import. To add more later, click Import monitors on the Vercel card. Imported monitors count toward your plan's limits.
3. Turn on deploy events
On the Vercel card in Settings → Integrations, click Webhook URL and copy it. The URL contains a secret, so treat it like a password. Then, in Vercel:
- Switch to your team, open Settings → Webhooks and click Create Webhook.
- Pick the events Deployment Error and Deployment Succeeded, and the projects you imported.
- Paste the URL and create it.
From then on, for every project you imported:
- A failed production deploy opens an incident. The previous deploy keeps serving, so it's a warning, not an outage.
- The next successful production deploy resolves it.
Preview deploys, and projects you didn't import, are ignored.
Vercel plans
4. Recover automatically
After the import, Create self-healing workflow builds a workflow with one branch per imported project: when that project's monitor opens an incident, the Vercel recovery step redeploys the previous production version. A redeploy can take as long as a build. Add a message step after it so a person knows it happened.
The step comes with guardrails:
- A resolved incident never triggers a redeploy.
- A cooldown between attempts on the same project, 10 minutes by default.
- At most 3 attempts per incident by default.
- If production is already running a version Uptimy redeployed, the step stops instead of going further back.
- Only projects you imported can be redeployed, whatever else the integration can see.
Every attempt, and every one skipped with its reason, is in the workflow's run details. See Workflows.
Connected with a token earlier?
Plans
Troubleshooting
- No incidents for failed deploys: check that the webhook is on the team the project belongs to, with both events picked, and that the project was imported. Only production deploys count.
- A recovery step failed: the run details show Vercel's answer. A project needs an earlier production deployment to redeploy.
- The installation is disabled: this usually means the person who installed it left the Vercel team. Choose Vercel under Settings → Integrations to connect it again.
Next steps
- Vercel cron job monitoring: heartbeats for your cron routes
- Status pages: publish the imported projects
- Incidents: how events become incidents