Deployments become events on the timeline.
Vercel webhooks need a Pro plan — the webhook section is locked on Hobby. On Hobby, post deploys from your coding agent instead.
The agent posts when it runs the deploy. If you push yourself, run the script by hand — or push a tag, which the GitHub hook picks up. Both routes put the same marker on the timeline, and the agent route gives you a better title than a commit hash.
target production is kept.deployment.succeeded.deployment.succeeded, production only. Kind deploy.
| Field | What it is |
|---|---|
kind | deploy |
title | Commit message, otherwise the deployment name, otherwise Production deploy. Clipped to 120 characters. |
external_id | Deployment id. |
occurred_at | Webhook createdAt. |
url | Deployment URL. |
meta.target | production |
meta.commit_sha | githubCommitSha, when present. |
meta.branch | githubCommitRef or branch, when present. |
HMAC-SHA1 of the raw body, hex, header x-vercel-signature.
Set it up under Settings → Webhooks in your project.