Configure webhook endpoint triggers
This is Step 2 in the procedure for creating Webhook endpoints triggered from an incident or an alert workflow.
Triggers in webhook endpoints are optional. Webhook endpoints are only triggered by workflows, so including a trigger in the webhook endpoint configuration only adds an additional level of filtering for the alerts or incidents. You can choose to use the workflow trigger of a data pipeline workflow by itself, or you can also include a trigger in the webhook endpoint to send a subset of the triggering alerts or incidents.
When adding a webhook endpoint trigger, use care to select a trigger that is compatible with the workflow configuration. Make sure you do not create a trigger with conditions that will never be met. For example, if you configure a data pipeline incident workflow to trigger when the assignee of an incident changes, then only the incidents where the assignee changed can trigger the webhook endpoint. If you also add a "tags changed" trigger to the webhook endpoint, then it will only send the incidents where the assignee changed and the tags changed.
Triggers for alert webhook endpoints | Triggers for incident webhook endpoints |
---|---|
An alert webhook endpoint trigger can be configured for the following field changes:
| An incident webhook endpoint trigger can be configured for the following field changes:
|