Need some help troubleshooting an EventBridge rule that is supposed to filter incoming events strictly for conversation.end events associated with a specific routing queue. We are building a downstream analytics pipeline in Singapore and only want to process transcripts for our premium support queue (queue-id-abc-123).
- Created an EventBridge rule using the AWS Console.
- Defined the event pattern JSON to match
source: genesyscloudanddetail-type: conversation.end. - Added a filter condition on
detail.queueIdto match our specific queue ID.
The rule triggers for every single conversation end event across the entire org, ignoring the queueId filter. Here is the pattern I am using:
{
"source": ["genesyscloud"],
"detail-type": ["conversation.end"],
"detail": {
"queueId": ["queue-id-abc-123"]
}
}
I verified via GET /api/v2/interactions/conversations that the queueId field is present in the payload. Is the path incorrect for the detail object? Or does the EventBridge consumer require a different attribute name like routing.queueId? The current setup is flooding our Lambda with irrelevant data.