Automate PagerDuty alerts in Slack/Cisco Webex Teams with webMethods.io Integration

Automate PagerDuty alerts in Slack/Cisco Webex Teams with webMethods.io Integration

Overview

Dive into this step-by-step guide and learn how easy you can build a workflow that automatically sends targeted notifications to your chosen Slack channel or Webex Teams space, not just for new PagerDuty incidents, but also for resolved, escalated, and reassigned ones.

Prerequisite:

Set up a trigger action

Login to your webMethods.io Integration tenant, create a new project or choose an existing one and create a blank workflow. If you need a refresher on how to get to this point, this guide can be a great introduction.

To set up the trigger action, click on the small setting icon on the Start step and choose the PagerDuty trigger.

PagerDuty action

PagerDuty action configuration

Select New incident as a trigger and complete the authorization – connect webMethods.io Integration with your PagerDuty account - you need to provide PagerDuty API Key which you can generate in your account under Integrations->API Access key.

Click Save. You should see the test trigger window.

To test your trigger, you need to perform the trigger action. Open PagerDuty and add new incident:

Create new incident

Go back to the webMethods.io Integration workflow and click Test. You should see the output data from the trigger which webMethods.io Integration will use to configure and test the rest of the workflow. Click Done.

Configure the notification step

You can now proceed with setting up the notification step – choose the app that best works for you, for example:

Slack

Add the Slack connector to the canvas with the drag and drop feature. This automatically connects with the PagerDuty trigger.

Search the Slack connector

Connect the Slack connector

Click on the small settings icon on the Slack connector, select Post Message to Channel as action and complete the authorization – connect webMethods.io Integration with your Slack account.

Slack connector action

Click Next.

Now you can proceed with the action configuration – choose the Slack channel type and then type the channel ID where you want to post a message. Type the message body – use the Incoming data panel to include incident information received from the trigger output:

Slack connector configuration

Click Next and then Done.

Cisco Webex Teams

Add the Cisco Webex Teams connector to the canvas with the drag and drop feature. This automatically connects with the PagerDuty trigger.

Search Cisco Webex Teams connector

Connect Cisco Webex Teams connector

Click on the small settings icon on the Cisco Webex Teams connector, select Post new message as action and complete the authorization – connect webMethods.io Integration with your Cisco Webex Teams account.

Cisco Webex Teams connector action

Now you can proceed with the action configuration – choose the Space ID where you want to post the message. Type the message body – use the Incoming data panel to include incident information received from the trigger output.

Cisco Webex Teams connector configuration

Click Next and then Done.

Once you are done with the notification configuration step, connect it to the Stop step and save your workflow:

Final workflow

Test the workflow

You can now run the workflow using the play button in the right upper corner and review the result. If you have configured the workflow correctly, you should see the newly created message in your Slack channel or your Cisco Webex Teams space:

Slack channel message

Cisco Webex Teams space message

Now every time a new incident is created in PagerDuty, a new message will be automatically posted in your Slack channel or Cisco Webex Teams space. Please note that this may take some time.

Other use cases

Other possible use cases – you can set notifications not only for new incidents but also for resolved/escalated/reassigned/delegated and more. Just choose the right trigger action and follow the rest of the tutorial steps:

PagerDuty triggers

Execution history

At the bottom-left corner of the screen you can find the Execution history of the workflow:

Execution history

From here you can monitor the execution status and view error details if needed:

Execution status

Please note that workflow execution logs must be enabled from the workflow execution settings:

Workflow settings button

Workflow settings

Read full topic