Notifiers

These essentially work like webhooks. In the admin section of the frontend, notifiers can be managed.

The notifier defines:

• Ext API Service
• URL path
• HTTP verb
• Custom payload in Jinja

These variables can be used in the Jinja template, they can be expected to be in the same format as on the API:

• service_instance
• cmdb_data
• callback_data

With notifiers in place, the Triggers configure the execution of the notifier.

By default, Triggers run on all Phase Instance changes and. But they can be restricted to run only:

• for specific phases
• for specific changes (e.g. deployed, error)

A Notifier may have multiple triggers, so that only specific PhaseInstance changes will result in submitting of the Notifier.

Sending notifiers will never result in an error, so carefully check the logs if they are not sent. Triggers can also be tested on the Notifier detail page.