Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Use a GitHub repository or organization webhook to sync deployments and releases to Flashduty On-call. Each deployment and each release becomes one Flashduty change; every state of a deployment, from created and queued through running to success or failure, updates that same change. GitHub Actions jobs that declare an environment create deployments automatically, so repositories that release with Actions can connect without changing their workflows.

​
In Flashduty On-call

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

​
Configure GitHub

1

Open webhook settings

  • Repository: go to the repository’s Settings → Webhooks and click Add webhook
  • Organization: go to the organization’s Settings → Webhooks and click Add webhook; events from every repository in the organization are sent
You need admin permission on the repository or organization.
2

Enter the Push URL

  1. Payload URL: paste the complete Flashduty integration Push URL
  2. Content type: select application/json (application/x-www-form-urlencoded is also accepted)
  3. Secret: leave it empty; Flashduty authenticates the request by the integration_key in the Push URL
3

Select events

  1. Select Let me select individual events
  2. Check Deployments, Deployment statuses, and Releases, and uncheck Pushes, which is selected by default
  3. Keep Active checked and click Add webhook
After you save, GitHub sends a ping. Flashduty accepts it without creating a change.

​
What one change is

​
Status mapping

Done, Failed, and Canceled are end states; Flashduty records the change’s end time when one arrives. These deliveries are accepted without creating a change: ping, any other event type, the release actions created, edited, released, and prereleased (GitHub also sends published when a release is published, and that is the one recorded), and the deployment state inactive (an older deployment replaced by a newer one; its earlier result stays as it was).

​
Change content

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

​
FAQ

  • Make sure the webhook has Deployments and Deployment statuses checked. Pushes alone creates no changes
  • Check the delivery history and Flashduty’s responses under Recent Deliveries on the GitHub webhook page
  • Only releases that use GitHub Deployments send deployment events, for example a GitHub Actions job that declares an environment, or a call to the Deployments API
No. An event with the same state and time is recorded once.
  • unsupported deployment_status.state: Flashduty received a deployment state it does not support yet. Contact us
  • deployment.id is missing or release.id is missing: the payload is incomplete. Make sure the delivery comes from a native GitHub webhook