Skip to main content

Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Vercel connector page.

How webhooks are set up

StackOne creates and manages the Vercel webhook automatically when the account is connected, and removes it when the account is disconnected. There is nothing to configure in Vercel and no URL to paste.

  • StackOne creates one team-wide webhook (all team projects) with the connection’s Access Token, subscribed to the events you enable in StackOne.
  • The webhook counts toward Vercel’s limit of 20 webhooks per team.

Available webhook events

The following Vercel events can be enabled. Only events selected in StackOne are included in the subscription, so Vercel does not deliver events that are not selected.

1

Review deployment events

Events about deployments of any project on the team.

  • Deployment Created (deployment.created) — Fired when a deployment starts.
  • Deployment Succeeded (deployment.succeeded) — Fired when a deployment succeeds, after any blocking checks pass.
  • Deployment Error (deployment.error) — Fired when a deployment fails.
  • Deployment Canceled (deployment.canceled) — Fired when a deployment is canceled.
  • Deployment Promoted (deployment.promoted) — Fired when a deployment is promoted to production, manually or automatically.
  • Deployment Rollback (deployment.rollback) — Fired when Vercel accepts an instant rollback request.
2

Review project events

Events about projects, their environment variables, their domains and rolling releases.

  • Project Created (project.created) — Fired when a project is created.
  • Project Removed (project.removed) — Fired when a project is deleted.
  • Project Renamed (project.renamed) — Fired when a project is renamed.
  • Project Environment Variable Created (project.env-variable.created) — Fired when a project environment variable is created.
  • Project Environment Variable Updated (project.env-variable.updated) — Fired when a project environment variable is updated.
  • Project Environment Variable Deleted (project.env-variable.deleted) — Fired when a project environment variable is deleted.
  • Project Domain Created (project.domain.created) — Fired when a domain is added to a project.
  • Project Domain Updated (project.domain.updated) — Fired when a project domain changes (redirect, Git branch or name).
  • Project Domain Deleted (project.domain.deleted) — Fired when a domain is removed from a project.
  • Project Domain Verified (project.domain.verified) — Fired when a project domain is verified.
  • Project Domain Moved (project.domain.moved) — Fired when a domain moves from one project to another.
  • Rolling Release Started (project.rolling-release.started) — Fired when a rolling release starts.
  • Rolling Release Approved (project.rolling-release.approved) — Fired when a rolling release stage is approved.
  • Rolling Release Completed (project.rolling-release.completed) — Fired when a rolling release completes.
3

Review domain events

Events about domains registered or managed on the team, their certificates and DNS records.

  • Domain Auto-Renew Changed (domain.auto-renew.changed) — Fired when auto-renew is turned on or off for a domain.
  • Domain Certificate Added (domain.certificate.add) — Fired when an SSL certificate is added for a domain.
  • Domain Certificate Deleted (domain.certificate.deleted) — Fired when a certificate is deleted.
  • Domain DNS Records Changed (domain.dns.records.changed) — Fired when DNS records of a domain change.
4

Review feature flag events

Events about feature flags and flag segments.

  • Flag Created (flag.created) — Fired when a feature flag is created.
  • Flag Updated (flag.updated) — Fired when a feature flag is updated.
  • Flag Deleted (flag.deleted) — Fired when a feature flag is deleted.
  • Flag Segment Created (flag.segment.created) — Fired when a flag segment is created.
  • Flag Segment Updated (flag.segment.updated) — Fired when a flag segment is updated.
  • Flag Segment Deleted (flag.segment.deleted) — Fired when a flag segment is deleted.

Delivery format

How Vercel delivers events to StackOne.

1

Inspect event payloads

Vercel sends one event per HTTP POST. The JSON body has type (the event code; for the four domain events Vercel writes it with hyphens, such as domain.certificate-add for domain.certificate.add), id (the delivery ID), createdAt (milliseconds since epoch), region and a payload object whose fields depend on the event; payload.team.id names the team. Vercel signs each request with the x-vercel-signature header and retries a failed delivery with exponential backoff for up to 24 hours.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.