Notifications

Send an email or a channel message when a job finishes or something happens to it

The notifications of a form say who hears about its jobs, and when:

  • Who: recipients, email addresses, and channels, the names of notification channels (mail, Slack, Microsoft Teams, Telegram, a webhook). At least one of the two is required.
  • When: onStatus, when a job ends (success, failed, aborted, warning, or any), and onEvent, when something happens to a job (launch, relaunch, delete, approve, reject, or any).
notifications:
  recipients:
    - ops@example.com
  channels:
    - ops-teams
  onStatus:
    - failed
  onEvent:
    - approve
    - reject

When you want to send a notification on job-event: an email, and a message to notification channels (Connections > Notifications: Slack, Microsoft Teams, Telegram, a webhook)

Email Templates
Notification emails use HTML templates located in server/templates/email/:

  • approval.html - Approval request notifications
  • jobstatus.html - Job outcome notifications (success, failed, aborted, warning)
  • jobevent.html - Job lifecycle event notifications (launch, relaunch, delete, approve, reject)

    These templates can be customized by replacing them with your own versions.
    In Docker or Kubernetes deployments, mount your custom templates to /app/dist/templates/email/ to override the defaults.
    Example Docker mount: -v /path/to/custom/templates:/app/dist/templates/email/
    A mount at the former location, /app/dist/src/templates/, keeps working and takes precedence.

Attributes

The attributes of the notifications object:

Attribute Comments
recipients
array

Recipients
email address

A list of email addresses who need to receive a notification.
recipients or channels, or both, is needed.
channels
array

Channels
the name of a notification channel

The notification channels of Connections > Notifications the notification goes to: Slack, Microsoft Teams, Telegram, a webhook. They get a short message (the form, the job, what happened) with a link to the job.
A mail channel in this list sends the notification mail to the recipients through that server instead of the active one.
A name that is not there is said in the log and skipped. (Added in 7.0.0)
onStatus
array

Jobstatus event

A list of jobstatus events you want to send a notification on. Use any, if you always want a notification.
At least one of onStatus or onEvent must be specified for notifications to be sent.

Choices:
  • any
  • success
  • failed
  • aborted
  • warning
onEvent
array

Job trigger events

A list of job lifecycle events (triggers) you want to send a notification on.
Unlike onStatus which notifies on job outcomes, onEvent notifies on user actions and job lifecycle events.
Use any to be notified of all job events.

Choices:
  • any
  • launch
  • relaunch
  • delete
  • approve
  • reject

Examples

Example notifications, in YAML:

1) Send a notification on failed

The definition, in YAML:

notifications:
  recipients:
    - info@ansibleguy.com
  onStatus:
    - failed

2) Send notifications on job events (launch, relaunch, approve, reject)

The definition, in YAML:

notifications:
  recipients:
    - admin@ansibleguy.com
    - auditor@ansibleguy.com
  onEvent:
    - launch
    - relaunch
    - approve
    - reject

3) Send notifications on all events

The definition, in YAML:

notifications:
  recipients:
    - admin@ansibleguy.com
  onStatus:
    - any
  onEvent:
    - launch
    - relaunch
    - delete
    - approve
    - reject