Welcome to the xMatters community!

We created this site for our customers and partners and we encourage you to explore, engage, and learn. To ensure that this community is fun and helpful, professional and respectful participation is expected... and troll-like behavior won't be tolerated.

In this premier installment, we'll define a few terms and go over all of the (currently) available methods for "integrations". In subsequent releases, we'll dive into each item in more detail and provide working examples.

We'll also dig into all the cool new technology toys the engineers have been cooking up and are just about ready to serve. So be sure to follow this page as I'll update it with links and technologies as we go.

Terms:

What is an "integration"? The term "integration" gets thrown around a lot and it means different things to different people. For this series, we'll talk about event integrations that are either "one way", "closed loop" or "webhook only".

One way integrations refer to integrations where the event starts in an external system, sends the payload to xMatters (either through the IA or directly to the REST API) and notifies the recipient. Recipients may or may not respond and their response is logged in xMatters, but that is where it stops. So there is no payload back to the management system. Period.

Compare this with closed loop integrations that follow the same path as the One Way integrations, but have an additional step of updating the management system either with delivery updates, event status updates or recipient responses.

Again, compare these with webhook-only integrations where the event originates in xMatters (probably through a Message panel), then through a webhook update an external system.

Additionally, there are data integrations that are used to synchronize data such as groups, shifts, users and/or devices from an external system to xMatters.