Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Use a Netlify project’s deploy notifications to sync deploys to Flashduty On-call. Each deploy becomes one Flashduty change; every notification of that deploy, from waiting for approval and building to success or failure, updates that same change. Production deploys, branch deploys, and Deploy Previews are all sent; the environment label tells them apart. HTTP POST request deploy notifications are available on every Netlify plan.

​
In Flashduty On-call

  1. In the Flashduty console, go to Integration Center → Change Events
  2. Select Netlify and enter an integration name
  3. To assign changes to specific channels, add rules under the integration’s Routes that match labels such as project or environment
  4. Click Save and copy the generated Push URL

​
Configure Netlify

Each Netlify notification listens to one event, so add one notification for each event in the table below, all with the same Push URL.
1

Open deploy notification settings

In your Netlify project, go to Project configuration → Notifications → Deploy notifications, click Add notification, and select HTTP POST request.
2

Enter the Push URL

  1. Event to listen for: select one event, see the next step
  2. URL to notify: paste the complete Flashduty integration Push URL
  3. JWS secret token: leave it empty; Flashduty authenticates the request by the integration_key in the Push URL
  4. Click Save
3

Add one notification per event

Deploy locked, Deploy unlocked, and Deploy deleted are not needed: they do not change a deploy’s result, and Flashduty accepts them without creating a change.

​
What one change is

A rollback (Deploy restored) publishes an existing deploy again, so it updates that deploy’s change with status Done. The rollback notification carries no rollback time, so the event time is when Flashduty receives it.

​
Status mapping

Done, Failed, and Canceled are end states; Flashduty records the change’s end time when one arrives.

​
Change content

Labels can be used in routes and to filter the change list:

​
FAQ

Each Netlify notification sends one event. Make sure Deploy started, Deploy succeeded, and Deploy failed each have their own notification.
No. When Netlify resends a notification that failed, Flashduty records it at the time of the event itself, and a notification with the same deploy, state, and time is recorded once. Deploy restored is the exception: it is recorded at the time Flashduty receives it, so a resent one is recorded again.
  • unsupported X-Netlify-Event: Flashduty received a Netlify event it does not support yet. Contact us
  • deploy id is missing: the payload is incomplete. Make sure the delivery comes from a Netlify deploy notification