Alert activity triggers

Examples of when to use this trigger:

• Automatically update the record in your monitoring tool to add an annotation that the xMatters alert ended.
• Post alert creation and termination updates to your reporting repository for analytics and observability initiatives.
• Automatically close the ticket in the source system when the xMatters alert ends.

Alert status trigger outputs

To see the payload behind the scenes, see the information for the equivalent trigger in the Integration Builder.

Examples of when to use this trigger:

• Post details about who was notified and when into a ticket, alert, or chat application so the notification process is clearly visible (and documented).
• Post details about device notification failures to a list so you can follow up with users who seem to be experiencing delivery issues.

Device delivery trigger outputs

To see the payload behind the scenes, see the information for the equivalent trigger in the Integration Builder.

Examples of when to use this trigger:

• Automatically assign an incident when a recipient responds with Accept (or Assign to me or whatever response you have configure for this).
• Approve or reject change requests based on responses.

Responses trigger outputs

To see the payload behind the scenes, see the information for the equivalent trigger in the Integration Builder.

To add response options to a Responses trigger:

1. Click + Add Response (or double-click the Responses parent) to add, remove, or edit response options.

2. Configure the response options and drag them into the order you want them to appear on the canvas, then click Save. In our MIM scenario, we added "Create major incident" and moved it to the top of the list.
   • For more information, see Create Alert step - Configure response options.
   • For more information, see Define response options for messaging forms.

Each response appears as a step on the canvas. You can now connect the steps you want to run when a recipient selects that response.

A few things to know about existing integrations:

• If you have an outbound integration that uses the Notification Responses trigger, it appears on the canvas but doesn't have the response options delineated since any actions based on different responses are handled in the outbound integration script.
• Some integrations use response options that are determined at runtime. We've updated our built-in integrations but some packaged or custom integrations still use these. For the time being, you'll need to continue to use an outbound integration using the Notification Responses trigger.
• For built-in integrations, you are unable to modify or delete the default response options included in the configuration; although you can add additional ones. To modify or delete built-in responses, you'll need to first convert the configuration to a workflow.

Examples of when to use this trigger:

• Post each comment to a Slack channel or another chat application.
• Populate the free-form text closure details of a ticket or alert (in this case, you could actually perform your response logic in the Alert Comment trigger instead of the response trigger!)
• Add the comments to a ticket or alert as annotations, recording the work performed on the alert, either for the next person in the resolution chain or for post-incident analysis.

Comments trigger output details

To see the payload behind the scenes, see the information for the equivalent trigger in the Integration Builder.

Examples of when to use this trigger:

• Automatically launch a new alert that warns a manager when an alert has escalated to the point where an SLA (service level agreement) is in jeopardy.
• Automatically update a chat room to warn team members when an alert is escalated.

Escalation trigger outputs

To see the payload behind the scenes, see the information for the equivalent trigger in the Integration Builder.

Examples of when to use this trigger:

• Automatically notify a chat room that an alert isn’t currently routing to on-call resources.

Targeted recipient failures trigger output details

To see the payload behind the scenes, see the information for the equivalent trigger in the Integration Builder.