Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Use a webhook notification template in AWX or Ansible Automation Platform (AAP) to sync runs of job templates and workflow job templates to Flashduty On-call. Each run becomes one Flashduty change; the run’s start and end update that same change. AWX cannot tell whether a template changes production, so enable the notification only on templates that deploy or modify things, not on read-only check templates.

In Flashduty On-call

  1. In the Flashduty console, go to Integration Center → Change Events
  2. Select AWX / Ansible Automation Platform 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 inventory
  4. Click Save and copy the generated Push URL

Configure AWX

1

Create a webhook notification template

Go to Administration → Notifications (in AAP 2.5 and later, Automation Execution → Administration → Notifiers) and click Add:
  1. Type: select Webhook
  2. Target URL: the full Push URL of the Flashduty integration
  3. HTTP Method: select POST
  4. Leave Customize messages at its defaults. The default message body is {{ job_metadata }}, the JSON description of the run, which is the format Flashduty parses
The Push URL already carries the integration key, so no username, password, or headers are needed.
2

Enable the notification on the job template

Open the job template or workflow job template to sync, switch to the Notifications tab, and turn on Start, Success, and Failure for the notification template you just created. All three are needed: Start makes the change appear when the run begins, Success and Failure give the end state, and without them the change stays in Processing.You can also enable the notification on an Organization to cover every template in it. Flashduty ignores the resulting project sync, inventory sync, and management job notifications.
3

Run the job

Save, then launch the job template; the change appears in the Flashduty change list. The Test button on the notification template sends a test message: Flashduty answers successfully but records no change, so it confirms the Push URL is reachable. AWX shows the result of each delivery in the notification template’s sent notifications.

How changes are merged

Each run of a job template or workflow job is one change, for example the run with job ID 4711.
  • The start and end notifications of one run update the same change
  • Two runs of the same template are two changes; a relaunch is a new run
  • Each job template run launched by a workflow is its own change
  • Create a separate integration per AWX instance, otherwise Flashduty merges the same job ID from two instances into one change

Status mapping

Done, Failed, and Canceled are end states; Flashduty records the change’s end time. With a custom message body, new maps to Planned, and pending and waiting map to Ready; the default body never sends these three.

Change content

Use labels for routing and for filtering the change list: Extra variables (extra_vars), credentials, and per-host results may contain sensitive data and are not recorded.

FAQ

  • Check that Start, Success, and Failure are all on in the job template’s Notifications tab
  • Check that Customize messages did not change the message body; when the body is not JSON, AWX sends an empty object {} and Flashduty rejects it
  • Open the notification template’s sent notifications under Administration → Notifications to see whether each delivery succeeded and which error came back
The end notification did not arrive. Check that the template has Success and Failure notifications on and that AWX can reach Flashduty. AWX does not resend a failed delivery.
Project syncs, inventory syncs, and management jobs (such as cleanup jobs) do not change production, so Flashduty answers successfully and records nothing. The same goes for workflow approval node notifications.
  • unsupported status: status is missing or is not an AWX job status. It also appears when the message body is not JSON, because AWX then sends {}
  • id is missing: the custom message body has no job ID. Keep the id field in the body