We’ve set up an EventBridge rule to catch conversations events from Genesys Cloud, but it’s not firing. The pattern looks right to me, but maybe I’m missing something subtle.
{
"source": ["genesys.cloud"],
"detail-type": ["Conversation Event"],
"detail": {
"conversationId": ["*"]
}
}
Any ideas on how to debug this?
The pattern you posted looks clean on the surface, but EventBridge is notoriously strict about nested object matching. The issue is almost certainly that detail isn’t a flat object in the actual payload coming from Genesys. When Genesys pushes to EventBridge via the integration, the detail field often contains sub-objects or arrays that your wildcard * in conversationId might not be catching correctly if the structure varies.
I ran into this exact headache last week while syncing call logs to S3. The conversationId might be nested deeper, or the event type inside detail changes based on whether it’s a voice or chat interaction. You need to check the actual raw event in CloudWatch Logs Insights. Don’t trust the “Test Event” button in the console; it often uses a simplified schema that doesn’t match the live stream.
Here’s what I did to fix it. I switched to a broader match on the detail-type and then filtered grammatically in the Lambda, rather than trying to do complex JSON path matching in the rule. It’s less efficient but way more reliable.
{
"source": ["genesys.cloud"],
"detail-type": ["Conversation Event"]
}
Then, inside your Lambda handler, inspect event.detail.conversationId. If that’s null or undefined, the structure is different. Also, double-check that your EventBridge partner event source is actually enabled in the Genesys Cloud admin console under Integrations > EventBridge. Sometimes the sync fails silently if the region doesn’t match. If you’re in us-east-1, ensure your EventBridge bus is there too. Cross-region pushes don’t work out of the box without extra config.
Check the CloudWatch logs for your Lambda. If the rule is firing but the Lambda isn’t, you’ll see invocations there. If there are no invocations, the rule pattern is definitely wrong. Try removing the detail block entirely and see if the rule triggers. If it does, you know the blem is the JSON structure, not the source.