Split Alerts

The built-in Split Alerts trigger initiates a flow when it receives a signal from a Split webhook.

Add the Split Alerts trigger to the canvas

  1. Go to the Triggers panel in the palette, expand the App Triggers section and drag the trigger onto the canvas.
  2. Double-click the trigger (or click the pencil icon).
  3. Set the authenticating user, and then copy the URL — you'll use this to set up the webhook in Split. Alternatively, you can create an integration user to use as the authenticating user.

  4. Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
  5. Click Done.
  6. On the flow canvas, connect the steps you want to run when xMatters receives a request to that URL.

You're now ready to configure Split to target the trigger.

Configure Split to send requests to the trigger URL

To have Split send alerts to the flow trigger, you need to configure a webhook and set it to use the trigger URL. 

Create an integration between Split and xMatters.

  1. In Split click your profile icon, then select Admin settings.

  2. In the Admin settings menu go down to Integration settings, and click Integrations.

  3. Go to Outgoing Webhook (Audit Logs) from the list of available integrations and click Add.

  4. Select the workspace for the integration from the Add drop-down menu.
  5. Specify the environment or environments you want the webhook to monitor in the Environments field.
  6. In the URL field, add the trigger URL you copied from Flow Designer.

  7. Add the target names of any recipients you want to notify when the alert fires.
    • For URL authentication, use an ampersand to attach recipients. For example, if you want to notify Emma Pearson and the on-call members in the group responsible for the Antares service, you'd add &recipients=epearson,antares to the end of the URL.
    • For other authentication types, use a question mark to attach recipients. For example, if you want to notify Barry Gull and the on-call members in the group responsible for the Cassiopeia service, you'd add ?recipients=bgull,cassiopeia to the end of the URL.
    • You must URL-encode any special characters or spaces in the target names.
  8. Optional: Click Send Test Message to test the trigger URL and recipients.
  9. Click Save.

You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use.

Outputs

The Split Changes trigger has the following outputs you can use as inputs to steps further along the flow.

Label

 Description

Recipients

 List of targeted recipients. Recipients are set by adding a recipients query parameter to the trigger URL.
Change Action

Action of the Split change. Available options are: 

  • Created the Split
  • Deleted the Split
  • Killed the Split
  • Reset the Split
  • Restored the Split
  • Updated the Split
Change ID Unique ID of the change.
Change Time Date and time the change took place in Split, in UNIX format.
Change Type

Type of change in Split. Available option is: 

  • FEATURE_TOGGLE
Comment Any additional user-provided comments for the change.
Current Split State State of the Split after the change occurred.
Description Description of the Split change.
Editor Username of the person who made the change in Split.
Environment ID Unique identifier of the Split environment.
Environment Name Name of the Split environment where the change occurred.
Link Direct link to the Split that was changed.
Previous Payload Contents of the previous Split payload.
Split Name Name of the Split where the change occurred.
Title Optional user-provided title for the Split change.
Raw Request JSON representation of the request. You can parse the raw request if you need additional details beyond the standard outputs.