Discover why PagerDuty users are switching to xMatters. Listen to insights from Ben Narramore, Director of Global Operations at PlayStation.Watch webinar

Uptime Blog

Details of Our Outbound Integrations

Re-imagining Incident Management with xMatters and Jira Ops

Outbound integrations are a powerful component of our Integration Platform. They facilitate closed-loop and compound integrations to update multiple third-party products and systems based on the outcome of xMatters notification events, notification deliveries, or responses.

Updates to these other systems are typically made using our ‘Callbacks” capability in xMatters and are often referred to as ‘webhooks’ in other systems. Our new release provides additional power and flexibility by simplifying how you create and configure outbound integrations.

Form callbacks retired
The process for configuring an outbound integration became more complex over time and required developers to navigate between different parts of the product. So We’ve replaced form callbacks with webhooks and moved their configuration into the Integration Builder, which means you now configure integrations from a single location in the xMatters web user interface.

We seamlessly migrated legacy callbacks into the Integration Builder and they’re 100% backward compatible with your existing integrations.

For more information about how xMatters will migrate legacy callbacks to the Integration Builder and what they’ll look like in the new release, see What’s going to happen to my old callbacks?

Multiple outbound integrations for the same form and trigger
In the old callback configuration screen it was only possible to have one action per trigger type (status updates, notification delivery updates, or response submissions), and that meant you could only send a callback to one URL, or execute one integration service. We weren’t fans of that limitation.

In the new workflow you define the trigger for each outbound integration during its configuration, so you’re no longer restricted to a single action for each trigger type. Instead, you can easily create compound integrations that update both source and downstream systems when a single trigger condition is met in xMatters. For example, you might want to create a compound integration that acknowledges an event in your monitoring tool and simultaneously opens an instant messenger session in your chat tool when a particular response is submitted.

Outbound integration actions
There are three available options for the action that an outbound integration can perform now that callbacks have been incorporated into the outbound integration workflow (click the links below to see a screenshot of the configuration steps for each action):

  1. Run a script – Execute a transformation script so you can integrate with any product over the web.
  1. Send a webhook (formerly known as ‘HTTP callbacks’) – Send a simple webhook to an HTTP endpoint. The webhook’s URL is defined using an endpoint, which means you’ll only have to update the base URL once if the hostname of a helpdesk, monitoring tool, or anything else you want to integrate with changes (for example, if you switch an integration from a test or staging environment to production).

‘Send a webhook’ outbound integrations are 100% backward compatible with the old HTTP Callbacks and will send the exact same JSON object as before.

  1. Send to Integration Agent – Facilitate the integration of xMatters communication plans with third-party products without requiring a hole to be opened in a corporate firewall to allow inbound communication.

Request a demo