The built-in BigPanda Incidents trigger initiates flows when it receives a request from a webhook in BigPanda.
- 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 BigPanda. Alternatively, you can create an integration user to use as the authenticating user.
- Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
- Connect the steps you want to run when xMatters receives a request to that URL.
You're now ready to configure BigPanda to target the trigger.
Configure BigPanda to send requests to the trigger URL
To have BigPanda send alerts to the flow trigger, you need to configure a webhook and set it to use the trigger URL.
Create an integration between BigPanda and xMatters.
- In BigPanda, navigate to the Integrations tab and click New Integration.
- Locate xMatters in the list of available integrations and click Integrate.
- Create an App Key. Give the integration a name, then click Generate App Key.
- Skip sections 2 - 7 on the BigPanda integration page as they are no longer required.
- In the Configure BigPanda section, paste the URL from the trigger in Flow Designer into the Callback URL field.
- If you use URL Authentication, continue on to the next step.
- If you use Basic Authentication, use the link on the BigPanda page to generate a Base-64 encoded authorization for the authenticating user. Paste the generated value after the word Basic in the Custom Headers section.
- Add the target names of any recipients you want xMatters to notify when the alert fires.
- For example, if you want to notify Emma Pearson, Mary McBride, and the on-call members in the Monitor Team responsible for the service, you'd add ?recipients=epearson,mmcbride,monitor%20team to the URL.
- You must URL-encode any special characters or spaces in the target names.
- Click Configure Webhook to save the integration.
Now that the integration is created, use BigPanda's Autoshare capabilites to share data from BigPanda.
- On the top right-hand side of the page, expand the Settings menu (represented by a gear icon) and click AutoShare.
- Click Create AutoShare.
- In the Create AutoShare window, set the following fields:
- Choose Environment: Expand the drop-down menu and select All.
- Escalate via: Expand the drop-down menu and select the xMatters integration you just created.
- Click Next.
- Optional: Add a message the AutoShare. The message is displayed in the Recent Activity section whenever BigPanda sends a signal to xMatters.
- 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 BigPanda Incidents trigger has the following outputs you can use as inputs to steps further along the flow.
|Recipients||List of targeted recipients. Recipients are set by adding a recipients query parameter to the trigger URL when you configure the webhook in BigPanda.|
|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/signals|
Activity level of the BigPanda incident. Available options are:
|Description||Description of the first alert.|
|Incident ID||Unique ID of the BigPanda incident.|
|Link||Direct URL to the incident in BigPanda.|
|Primary Property Name||Primary property name from the first alert.|
|Primary Property Value||Primary property value from the first alert.|
|Secondary Property Name||Secondary property name from the first alert.|
|Secondary Property Value||Secondary property value from the first alert.|
|Source System||Source system that initiated the incident in BigPanda.|
|Started On||Time the incident started in BigPanda in UNIX format.|
Status of the incident in BigPanda. Available options are:
|Raw Request||JSON representation of the request that can be parsed separately to get additional context on outputs.|