The built-in Moogsoft trigger initiates flows when it receives a request from a webhook in Moogsoft.
- Go to the Triggers tab in the palette, expand the App Triggers section, and drag the trigger onto the canvas.
- Double-click the trigger (or click the pencil icon).
- Set the authenticating user, and then copy the URL — you'll use this to set up the webhook in Moogsoft. Alternatively, you can create an integration user and use it as the authenticating user.
- Connect the steps you want to run when xMatters receives a request to that URL.
You're now ready to configure Moogsoft to target the trigger.
To have Moogsoft send alerts to the flow trigger, you need to configure a webhook and set it to use the trigger URL.
- In Moogsoft, go to Data Confg and select Integrations from the menu:
- Under Outbound Integrations, select Webhook to create a new webhook.
- Give the webhook a name (for example, xMatters).
- In the URL field, paste the trigger URL from the trigger.
- In the Parameters tab, add a recipients parameter with the recipients in a comma-separated list. For example, if you want to notify Emma Pearson, Mary McBride, and the members of the Monitor Team responsible for the service, you'd add epearson,mmcbride,monitor%20team. You must URL-encode any special characters or spaces in the target names.
- Optional: If you want to use Basic Authentication, go to the Authorization tab, select Basic Auth from the Authorization Type drop-down menu, and complete the Username and Password fields.
- Copy and paste the following into the Body tab:Copy
- Click Save.
You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use.
The trigger has the following outputs you can use as inputs to steps further along the flow.
|List of targeted recipients.|
|Signal Mode||Determines the flow path to follow, based on the value of the Status parameter.|
|Signal ID||Key or identifier used to terminate or correlate events or signals.|
|Description||Description of the alert or incident generated by Moogsoft.|
|ID||Unique ID of the alert or incident in Moogsoft.|
|Services||Services related to the alert or incident.|
|Severity||Severity of the alert or incident in Moogsoft.|
|Status||Status of the alert or incident.|
|Timestamp||Time the alert or incident started in Moogsoft.|
|Raw Request||JSON representation of the request that can be parsed separately to get additional context on outputs.|