This guide describes how to set up a webhook that sends Cmd data directly to xMatters. For general information about Cmd webhooks, see configuring webhooks.
Refer to the xMatters webhooks documentation here. By following those instructions, you will create an
Inbound Webhook Configuration URL, and decide which xMatters users will see incoming webhooks from Cmd. Save the URL for later.
Note: You should ignore the
Two-way Communication section of the xMatters setup process.
Confirm that you are in the correct project by reviewing the name of the current project in the top-right corner of the page.
Note: To learn more, see Switching between projects.
In the top-right corner, click the current project's name to open the drop-down menu.
Select Project & app settings.
On the left-hand menu, under the 'Project settings' section, select Integrations preferences.
Click Add integration in the top-right corner.
Give your integration a name to identify it in the Cmd web app (e.g. “xMatters webhook”).
Webhook URL, input the following: https://us-central1-cmd-production.cloudfunctions.net/xmatters-forwarder
Custom JSON to send, input the following, with the webhook URL you copied from xMatters instead of XMATTERS_WEBHOOK_URL_HERE:
CQL properties to send, select the data that Cmd will send to xMatters. You should include at least the following:
At this point, your configuration window should look similar to this:
Run the webhook test command in a terminal to test your webhook. If all is well, the users you selected in xMatters will receive an email like this one:
Assuming that worked, go back to Cmd and click Save on the webhook configuration window.
Now, you can configure any of your triggers to send alerts to xMatters. To do so, add the action “Send custom webhook alert” to a trigger, and make sure to select the intended integration. For example, the following trigger action creates a notice and sends an alert to a webhook named “xMatters integration”: