This enhancement extends the ServiceNow xMatters Integration v2 by incorporating ServiceNow Major Incident Management into the xMatters notification process.
With this update, notifications can now be triggered not only for Major Incidents but also for Incident Tasks and Incident Communication Tasks, providing greater flexibility in how incidents are communicated and managed.
- ServiceNow App Version: Everbridge Flow Designer
- xMatters ServiceNow Integration v2: Install Instructions
- ServiceNow Major Incident Plugin: Install Instructions
- xMatters Account:
- Required. If you don’t have one, sign up before proceeding.
The following update sets are provided:
ServiceNowMIMBusiness Rules (update XML)ServiceNowFlowDesignerv2-MajorIncidentWorkbench.zip
-
Triggering Notifications:
- xMatters notifications are created only once a Major Incident is changed to Proposed or Accepted in ServiceNow.
-
Non-Triggering States:
- Cancelled or Rejected Major Incidents will not trigger notifications.
-
Process Control:
- Ensures only reviewed and approved Major Incidents generate notifications, preventing noise from unapproved incidents.
-
Incident Task:
- Notifications can be triggered when ServiceNow Incident Tasks (e.g., investigation, resolution, or follow-up work items) are created or updated and an assignment group is assigned.
- The trigger profile uses the ServiceNow Record Alerts Incident Task
[incident_task]option in Flow Designer (see screenshot).
-
Incident Communication Task:
- Notifications can also be triggered for Incident Communication Tasks to ensure stakeholders and communication teams are alerted promptly.
- These follow a similar trigger profile structure, allowing separate workflows for technical responders vs. communication recipients.
- Log in to your ServiceNow instance with an administrator role.
- In the left-hand navigation, search for and click on Retrieved Update Sets under the System Update Sets group.
- On the Retrieved Update Sets page, scroll to the Related Links section and click Import Update Set from XML.
- On the Import XML page:
- Click Choose File.
- Select your update set
.xmlfile from your computer. - Click Upload.
- After the upload, find your newly uploaded update set on the Retrieved Update Sets page.
- Click the name of the update set to open its record.
- Click Preview Update Set in the upper-right corner to assess its suitability for your instance.
- If there are preview errors, they will appear in the Preview Problems related list.
- Select the error.
- From the Actions on selected rows menu, choose Accept remote update to resolve it.
- Once the preview is successful, click Commit Update Set to apply the changes to your instance.
- Close the progress dialog box after the commit is complete.
Verify that the Major Incident Plugin is active in your ServiceNow instance.
- Log into xMatters as a user with the Developer role.
- Navigate to Workflows.
- Click the Import button (top right).
- Import the file: ServiceNowFlowDesignerv2-MajorIncidentWorkbench.zip
Configure trigger profiles for:
- Incident Task
- Incident Communication Task
To create a trigger profile, navigate to:
Everbridge Flow Designer → Global Settings → Trigger Profiles
-
Click New in the upper-right corner of the page.
-
Complete the following fields:
- Name:
Incident Tasks - Credentials: Select the configured xMatters Credentials for this integration.
- Workflow: Choose the workflow from the populated list
(e.g., ServiceNow (Flow Designer) v2 – Major Incident Workbench). - Trigger: Select the trigger for Incident Tasks
(ServiceNow Record Alerts Incident Task[incident_task]). - Trigger URL: Automatically filled once you select a trigger.
- Default Alert Priority: Select a default priority (e.g., Medium).
This value will be sent to Flow Designer unless overridden by the integration. - Default Signal Mode (Optional): Enter a signal mode value.
This may be overridden if an incident is created or updated. - Additional Recipients: Enter one or more users or groups from xMatters or Everbridge who should also receive alerts.
(Separate recipients with commas). - ServiceNow API User: Select the ServiceNow user account that Flow Designer will use to send updates back to ServiceNow.
- Name:
-
Click Submit to create the trigger profile.
-
Click New in the upper-right corner of the page.
-
Complete the following fields:
- Name:
Incident Communication Task (sys_email) - Credentials: Select the configured xMatters Credentials for this integration.
- Workflow: Choose the workflow from the populated list
(e.g., ServiceNow (Flow Designer) v2 – Major Incident Workbench). - Trigger: Select the trigger for Incident Tasks
(ServiceNow Record Alerts Incident Task[sys_email]). - Trigger URL: Automatically filled once you select a trigger.
- Default Alert Priority: Select a default priority (e.g., Medium).
This value will be sent to Flow Designer unless overridden by the integration. - Default Signal Mode (Optional): Enter a signal mode value.
This may be overridden if an incident is created or updated. - Additional Recipients: Enter one or more users or groups from xMatters or Everbridge who should also receive alerts.
(Separate recipients with commas). - ServiceNow API User: Select the ServiceNow user account that Flow Designer will use to send updates back to ServiceNow.
- Name:
-
Click Submit to create the trigger profile.
Verify functionality by creating:
- A Proposed Major Incident
- An Approved Major Incident
- An Incident Task and Incident Communication Task
- These should trigger based on workflow selection.
flowchart TD
A[Major Incident Created] --> B{State?}
B -->|Proposed/Accepted| C[Trigger xMatters Notification]
B -->|Cancelled/Rejected| D[No Notification]
C --> E[Notify Technical Responders]
C --> F[Notify Stakeholders]
subgraph Incident Task Flow
G[Incident Task Created/Updated] --> H{Assignment Group Assigned?}
H -->|Yes| I[Trigger xMatters Notification for Task]
H -->|No| J[No Notification]
end
subgraph Communication Task Flow
K[Incident Communication Task Created/Updated] --> L[Trigger xMatters Notification for Comms]
L --> M[Notify Communication Teams]
end