Skip to main content

Configure the external endpoint for an incident webhook

This is Step 3 in the procedure for creating an incident webhook triggered from an incident workflow.

Complete the Endpoint configuration:

Request method

Select the request method (POST, PATCH, DELETE, PUT) to use to send data to the target system when an incident or alert is created which passes the filter defined in the first section.

URL

The URL of the endpoint on the external target system that receives information from Moogsoft Cloud.

Authorization

Select the way to authenticate with your target system.

You can choose from:

  • No auth

  • Basic Auth

  • Bearer Token

Note

Save your authorization credentials in the secure, encrypted Credential Store instead of adding them to the headers.

Saving credentials in the Credential Store also allows you to reuse them with other webhooks.

Headers

By default, headers include Content-Type: application/json. If there is other information that you would like to include in headers, you can define it here by clicking Add New Row. You can include as many additional rows as you need.

Headers consist of key : value pairs, where the key is the name of the header and the value is the contents.

You can use substitution syntax in both the key and value fields of a header. This is useful if you want the contents of your header to include field values from the incident that triggers your webhook. Note that the contents of the key field cannot be a list.

Example: Suppose your webhook is triggered by incidents that have the following property1 tag:

"tags": {
      "property1": [
        "string"
      ]
}

To substitute property1 in the value field of an outbound incident webhook header, you can create a new header with the following key : value pair:

  • key: headerName

  • value: The value of property1 is ${tags.property1[0]}

For more examples and information on using substitution syntax, read Substitution syntax.

In this section: