Hi ​@mraja,

I think it’s possible to achieve this by combining PagerDuty Event Orchestration with Rundeck automation. Set your orchestration rule to suppress the alert (so no incident is created), and add a webhook action that triggers a Rundeck job. The Rundeck job can then send a custom Slack notification using Slack’s API or Incoming Webhooks. This way, you get notified in Slack for the event, but no PagerDuty incident is triggered.

Here’s an example Workflow

• Event comes into PagerDuty.
• Orchestration rule matches, suppresses the alert, and triggers a webhook to Rundeck.
• Rundeck job runs, parses the event data, and sends a Slack notification.

Example Rundeck Job Script (Bash)

Here’s a simple example of what the Rundeck job step might look like:

#!/bin/bash

# Variables from webhook payload
EVENT_SUMMARY="${RD_OPTION_EVENT_SUMMARY}"
SLACK_WEBHOOK_URL="https://hooks.slack.com/services/your/webhook/url"

# Send message to Slack
curl -X POST -H 'Content-type: application/json' \
  --data "{\"text\":\"PagerDuty Event: $EVENT_SUMMARY\"}" \
  $SLACK_WEBHOOK_URL

I’ve added links to docs where it makes sense so it’s easier for you to figure a solution. Please let me know if this works for your case and have a nice day!

Hi ​@lupimiguel 

Thank you so much for sharing the documents. We will try this approach and let you know.