Integrations · Vercel

Vercel deployment notifications on your phone

A push when a deployment succeeds, errors or is promoted, for the projects you choose. Pro and Enterprise teams.

Vercel's own page was read on 12 September 2026 for every step below. If a menu has moved since, write to hello@youlmk.com and it is corrected the same day.

What Vercel sends

Deployment created, succeeded, promoted, rolled back, errored or cancelled; project and feature flag events; firewall attacks; as JSON with a type, a timestamp and a payload.

What arrives in the inbox

Title
The event's type in words ("Deployment succeeded", "Deployment error")
Priority
normal; set the source's Reach to Banner or Break through for the errors that matter
Group
the event type, so a run of the same event becomes one card

Set it up

In YouLMK, create a source of type webhook named after the service, and copy its webhook URL: youlmk.com/w/k_7hq2nk3f9qd8w4 with your own key. Then:

  1. In the Vercel dashboard, choose the team, then Settings, then Webhooks. Vercel offers account webhooks to Pro and Enterprise teams.
  2. Select the events (Deployment Succeeded and Deployment Error are the useful two), then the projects to listen to.
  3. Paste your source's webhook URL from YouLMK as the endpoint URL and click Create Webhook.
  4. The dialog shows a secret once; YouLMK does not need it, since the door reads the event, not the signature, for Vercel.

Make it quiet where it should be

Everything above lands with the source's own rules: its Reach (Silent, Badge, Banner, Break through), whether quiet hours hold it, and grouping of repeats into one card. Set them once on the source, in the app or at app.youlmk.com; the service never has to change. Unknown fields arrive as rows on the card, up to six; the whole request is capped at 8 KB (Webhooks).

Try it

The trial is 10 notifications and 3 watches, no card. Get your key, or read the webhooks reference first.

Source

vercel.com/docs/webhooks, Configure a webhook, read 12 September 2026.