Docs · Publishes

Vercel

Every deploy is checked the moment it goes live.

What it watches

Vercel feeds PublishesEvery deploy gets a verdict within five minutes — as Publish Verification.

What Keelnest reads

Access token · read projects and deployments, deploy webhooks.

Project-level deploy webhooks historically required an Integration; we use account-level webhooks.

Read-only, like every connection: Keelnest never refunds, charges, changes a price, edits a setting or an environment variable, merges on its own or runs a migration. The credential is checked with one read call before it is stored, encrypted at rest, and can be revoked at the provider at any time. Security says the whole of it.

How to connect

  1. Create the access token. Vercel > Account Settings > Tokens > Create. Scope it to the team that owns the projects; read is enough. Open Vercel.
  2. Paste it into Keelnest. In your workspace, open Integrations, find Vercel and press Connect. Keelnest makes one read call to confirm the credential works, stores it encrypted, and starts reading on the next five-minute tick.
  3. Link the apps. Under Manage, pick which applications this account watches. An app linked to a host is checked the moment that host reports a deploy; an app linked to a payment or AI account starts building its baseline from that hour.

Deploy notifications

Vercel can be told to call Keelnest when a deploy finishes, so verification starts within seconds of it instead of on the five-minute poll.

Where to set it up. Vercel → your team → Settings → Webhooks → Create: the address below, event “Deployment Succeeded”, scoped to the projects you want watched. Vercel shows a signing secret as it creates the webhook; copy it before you leave the page, because it is not shown again.

The address and the secret to paste are shown in Keelnest under Integrations › Vercel › Manage, one pair per connected account.

How a delivery is checked. x-vercel-signature: HMAC-SHA1 of the raw body with the webhook secret Vercel shows once, as it creates the webhook. A delivery is never trusted on its own: it says which site to look at first, and every fact about the deploy is then read back from Vercel’s API, so a forged or missed delivery changes nothing the next poll would not correct.

Account-level webhooks are a Pro or Enterprise team feature, and a team may have up to twenty. On a Hobby team there is no webhook to create and the five-minute poller is the only route.

Source: Vercel’s documentation.

Start watching

Create a workspace and connect Vercel from Integrations, or run the free check on any public URL first. All docs.