Using Webhooks to Alert Slack/Teams Channels on Queue Threshold Breaches

How-To-Articles
1

Using Webhooks to Alert Slack/Teams Channels on Queue Threshold Breaches

Executive Summary & Architectural Context

In an intense contact center environment, Supervisors cannot spend 8 hours a day staring at a wallboard waiting for a queue to breach SLA. If the “IT Helpdesk” queue suddenly spikes to 50 waiting calls, the Command Center needs an instant, proactive alert pushed to the tools they already use: Slack, Microsoft Teams, or PagerDuty.

Genesys Cloud provides an internal Alerting engine, but its native outbound actions are limited to Email or SMS. To push rich, formatted alerts directly into an external collaboration platform, you must architect a Webhook Integration.

This masterclass details how to configure Genesys Cloud Rule thresholds, parse the internal alerting payload, and use a Data Action Webhook to inject real-time JSON payloads into a Slack or Microsoft Teams channel.

Prerequisites, Roles & Licensing

  • Licensing: Available on all Genesys Cloud CX tiers.
  • Roles & Permissions:
    • Alerting > Alert > Add/Edit
    • Integrations > Action > Edit
  • Platform Dependencies:
    • Admin access to Slack or MS Teams to generate an Incoming Webhook URL.

The Implementation Deep-Dive

1. Generating the Destination Webhook (Slack Example)

First, you need the receiving URL.

  1. Open Slack, go to Apps, and search for Incoming Webhooks.
  2. Add it to a specific channel (e.g., #cc-command-center).
  3. Copy the Webhook URL (e.g., https://hooks.slack.com/services/T000...).
  4. Note: MS Teams follows an identical process via the “Connectors” menu on a channel.

2. Creating the Webhook Data Action in Genesys Cloud

Genesys Cloud needs a vehicle to fire the HTTP request.

  1. Navigate to Admin > Integrations > Integrations. Add the WebServices Data Actions integration.
  2. Go to Actions and click Add Action. Name it Alert_Slack_Webhook.
  3. Setup > Contracts:
    • The Input contract defines the variables you want to push from the Alert.
{
  "type": "object",
  "properties": {
    "QueueName": { "type": "string" },
    "WaitCount": { "type": "string" },
    "AlertMessage": { "type": "string" }
  }
}
  • The Output contract can be empty, as this is a fire-and-forget payload.
  1. Setup > Configuration > Request:
    • Set the URL to your Slack Webhook URL.
    • Set the Method to POST.
    • The body is where you format the Slack message layout using their specific Markdown syntax:
{
  "requestUrlTemplate": "https://hooks.slack.com/services/T00...",
  "requestType": "POST",
  "headers": {"Content-Type": "application/json"},
  "requestTemplate": "{\"text\": \":rotating_light: *SLA BREACH ALERT* :rotating_light:\\n*Queue:* ${input.QueueName}\\n*Calls Waiting:* ${input.WaitCount}\\n*Details:* ${input.AlertMessage}\"}"
}

3. Configuring the Alert Rule

Now you must define the mathematical threshold that triggers the Data Action.

  1. Navigate to Performance > Workspace > Alerts (or Admin > Routing > Rules).
  2. Create a new Alert Rule.
  3. Metric: Select Interactions Waiting.
  4. Condition: Greater Than 20.
  5. Target: Select your specific Queue (e.g., IT_Helpdesk).
  6. Notification Action: This is the crucial step. Instead of selecting “Email”, click Add Webhook.
  7. Select your Alert_Slack_Webhook Data Action.
  8. Map the alert variables to the Data Action inputs. Genesys Cloud exposes system variables to the alert engine.
    • QueueName → {{alert.entityName}}
    • WaitCount → {{alert.metricValue}}
    • AlertMessage → Wait time has breached acceptable SLA limits.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Alert Flooding

If the queue hits 21 waiting calls, it fires the Slack alert. If one call is answered (drops to 20), and then immediately another call arrives (back to 21), it fires a second alert. A fluctuating queue will spam the Slack channel with hundreds of notifications, leading to alarm fatigue.

  • Solution: In the Alert Rule configuration, you must define a Recurrence Interval or Hold-Off Timer. Configure the rule so that once triggered, it cannot re-trigger for the same queue for at least 15 minutes, giving the floor managers time to react and clear the backlog.

Edge Case 2: Escaping JSON in the Payload

If your AlertMessage contains a literal double-quote character, or if a queue name has strange characters, it will break the JSON structure in the requestTemplate of your Data Action, resulting in a 400 Bad Request from Slack.

  • Troubleshooting: Always use the built-in Velocity macro $esc.jsonString() inside your Data Action Request Template to sanitize variables before injecting them into the JSON body.
  • Corrected Template: "*Queue:* $esc.jsonString(${input.QueueName})"

Official References