Struggling to figure out why the Slack API rejects the payload generated by my custom Data Action when triggered by a queue SLA breach webhook. The Genesys Cloud webhook fires correctly, but the subsequent HTTP POST to Slack returns a 400 Bad Request with invalid_blocks.
I am using a Data Action to transform the Genesys webhook payload into the Slack Block Kit format. The issue seems to be in the JSON path mapping for the text field within the mrkdwn object. Here is the relevant portion of my Data Action configuration:
{
"type": "http",
"method": "POST",
"url": "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
"body": {
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Queue: {{data.queueName}} | Breach: {{data.breachDuration}}s"
}
}
]
}
}
The error from Slack is:
invalid_blocks: blocks in payload are invalid
I have verified the JSON structure against the Slack docs. Is there a specific encoding issue with the {{data.*}} expressions in Genesys Data Actions when sending to external webhooks? Or is the webhook payload from Genesys not providing the expected queueName field in the SLA breach event?