If this is a new connection you will usually only have the ability to use the ‘Provide a sample payload' option to manually provide an expected payload. If you are modifying an existing connection, you may be able to 'Use the last received payload’ to use live details.

Lots of providers will give you sample JSON from their webhooks that you can easily copy and paste into the sample payload screen to give you content to work with. If you don’t have that available, you could create the connection using simple values, wait for a connection to be made, and then modify the connection to specification.

The 'Target Object' page provides you with the ability to configure how events are raised against objects in SCOM.

Raising the events against the webhook object itself is the default option and proves you with a good catchall solution for any scenario where you cannot (or do not want to) associate the events with a specific object in SCOM.

Selecting the ‘Raise Events on Dynamic Objects' option gives you the 'Search Criteria Template’ with which you can associate your events to a specific object.

Use the Browse button to pick a class to associate the query with.

Using the ‘Liquid Template Language’ you can pull in and manipulate the details from your webhook, then use them in SCOMs 'Criteria Expression Syntax’ to associate the event with.

Use the Test Criteria button to check your work!

The 'Event Channel' page allows you to set the channel that is used on your events.

The Channel field is limited to 255 characters by the underlying database.

Selecting the 'Dynamic Value' option allows you to populate this dynamically using details pulled in from the webhook using the ‘Liquid Template Language’ for manipulation where required.

The field cannot accept a null value so where this occurs in a dynamic template it will be replaced with the default value.

As you might expect, the 'Event Number' page allows you to set the event number that is used for your events.

This field is an integer and can be set from 0 to 65526.

Should you wish to set this dynamically, the 'Dynamic Value' option has your back. This option allows you to manipulate the details pulled in from the webhook using the ‘Liquid Template Language’ for manipulation where required.

The field cannot accept a null value so where this occurs in a dynamic template (or if the type returned is incorrect) it will be replaced with the default value.

The 'Event Level' page is where you set the level of the event you wish to raise.

This is an integer, and though we’re not aware of any limits outside of this, it’s best practice to stick with one of the standard enumeration values.

Like all of the other pages that support it, the 'Dynamic Value' option allows you to use the ‘Liquid Template Language’ to manipulate and pull in details from your webhook to use here.

The field cannot accept a null value so where this occurs in a dynamic template (or if the type returned is incorrect) it will be replaced with the default value.

The 'Logging Computer' page is where you set the field of the same name.

This is a simple string value that can be set up to 400 characters in length and cannot be null.

The 'Dynamic Value' option lets you manipulate the webhook data to fill in this property using the ‘Liquid Template Language’.

As the field cannot be null the default value will be used as a fallback should the Liquid fail to return anything.

The 'User' page is where you can set the User field for your event.

This is a simple string value that can be up to 255 characters in length and cannot be null.

As usual, the 'Dynamic Value' option lets you pull in the required data from your webhook using the ‘Liquid Template Language’.

As the field cannot be null the default value will be used as a fallback should the Liquid fail to return anything.

The ‘Event Description' provides you with the meat of your event, its description.

The ‘Event Description Template' is where you can really shine. Using the 'Liquid Template Language’ you can customize this description to make the best use of the data passed in via the webhook, allowing you to generate dynamic and truly useful descriptions from your ingested data on the fly.

The Management Pack page allows you to select where your configuration will be stored.

By default, we store your configuration in a dedicated management pack. However, you are free to choose your own management pack (including creating a new one). You can also export the configuration to XML for use in change management processes or other reasons.

Finally, you will be brought to the summary screen where you can look over the configuration for a final time before finishing the wizard.

Should you wish to go back and change any part of your configuration, you can use the ‘Previous’ button or jump directly to the relevant page using the links on the left.