Netlify Webhook Setup Guide

The Native Webhook URL is generated once an account has been linked.

• Open the linked account in StackOne.
• Copy the value from Native Webhook URL.

Sign in to your Netlify account and open the site you want to receive events from.

• Go to Project configuration > Notifications > Emails and webhooks.

Under Emails and webhooks, click Add notification and select HTTP POST request.

• Event to listen for: select one of the events listed below.
• URL to notify: paste the StackOne Native Webhook URL.
• Leave JWS secret token empty. StackOne does not verify it.
• Click Save.

Each Netlify notification sends one event. Add a notification for every event you want StackOne to receive.

Events related to site deploys, deploy locking and deploy requests from untrusted contributors.

• Deploy Started (deploy_building) — Fired when a Netlify deploy starts building
• Deploy Succeeded (deploy_created) — Fired when a Netlify deploy finishes and is ready, and is published if auto publishing is on
• Deploy Failed (deploy_failed) — Fired when a Netlify deploy does not complete
• Deploy Deleted (deploy_deleted) — Fired when a Netlify deploy is deleted
• Deploy Locked (deploy_locked) — Fired when auto publishing is locked to a deploy, keeping the site on that deploy
• Deploy Unlocked (deploy_unlocked) — Fired when auto publishing is unlocked on a site
• Deploy Restored (deploy_restored) — Fired when a previous deploy is manually published again
• Deploy Request Pending (deploy_request_pending) — Fired when a deploy from an untrusted contributor is waiting for approval
• Deploy Request Accepted (deploy_request_accepted) — Fired when a pending deploy request from an untrusted contributor is approved
• Deploy Request Rejected (deploy_request_rejected) — Fired when a pending deploy request from an untrusted contributor is rejected
• Deploy Failed After Succeeding (deploy_failed_after_succeeding) — Fired when a deploy fails when the previous deploy of the site succeeded
• Deploy Succeeded After Failing (deploy_succeeded_after_failing) — Fired when a deploy succeeds when the previous deploy of the site failed

Events related to Netlify Forms.

• Form Submission Created (submission_created) — Fired when a Netlify Forms submission is received, excluding submissions flagged as spam

Events related to split tests, which divide site traffic between branches.

• Split Test Activated (split_test_activated) — Fired when a split test, which splits traffic between branches, starts on a site
• Split Test Deactivated (split_test_deactivated) — Fired when a split test is stopped on a site
• Split Test Modified (split_test_modified) — Fired when the branches or traffic split of a split test change

Events related to Netlify dev servers, used by Agent Runners and Visual Editor.

• Dev Server Created (dev_server_created) — Fired when a Netlify dev server, used by Agent Runners and Visual Editor, is created for a site
• Dev Server Live (dev_server_live) — Fired when a Netlify dev server finishes starting and is live
• Dev Server Stopped (dev_server_stopped) — Fired when a Netlify dev server is stopped
• Dev Server Failed (dev_server_failed) — Fired when a Netlify dev server fails to start or crashes

Netlify sends one event per HTTP POST with a JSON body. The event name is carried only in the X-Netlify-Event header (for example deploy_created). The body is the affected record itself (a deploy, form submission, split test or dev server), and StackOne uses its ID as the event ID, so a deploy can be fetched by its deploy ID.