Flow tools

Tools are steps that evaluate the information coming through the flow and use it to decide what action to take next.

Tools help you create richer, more refined flows adapted to your use cases. Switch steps split a flow onto different paths (for example, use path A if the event is customer impacting but use path B if it's not). The xMatters Create Event step creates a new event in the middle of a flow, using information from the previous steps to populate the notification details and targeted recipients. You can even combine them to only create an xMatters event when a property has a certain value.

Switch step

A switch step functions like the switch on a set of railway tracks. It determines which route the train — or flow — needs to take next. You can base this decision point on the value of event properties, trigger outputs, constants, or outputs of previous steps in the flow.

Here are a few examples of how you can use a switch step:

  • The value of a "Severity" property: "Critical" goes one way, "High" another, everything else follows a third, default path.
  • A success response from a Create Ticket step: "201" continues the flow, while "400" sends a notification that something went wrong.
  • The value of a "Team" property: "Alpha" follows one path that includes a "Post to Alpha Chat" step and "Beta" follows another path that posts to the Beta Chat channel.

xMatters Create Event

The xMatters Create Event step lets you create a new event at any point in the flow in response to previous steps, using information from those steps to populate event details and targeted recipients. You can target either the form the flow belongs to or another form in the communication plan.

For example, you might want to create a new event: 

  • In response to an email trigger, with the addressees in the email becoming the recipients of the event notification.
  • Based on an "Emergency alert - Location" switch step, creating events targeting different groups with different instructions if the location is Los Angeles versus London.
  • After an HTTP trigger, populating the event details using properties in the request, including setting the recipients from an "Assignment Group" output on the trigger.
  • Create an event using a different form that targets your customer support team after a "Customer Impacting" switch step.