Could someone explain why my AWS EventBridge rule is not matching Genesys Cloud events? I am migrating from Five9 and trying to replicate their real-time alerting using EventBridge instead of webhooks. I have configured the EventBridge integration in GC settings and set up a rule with the following event pattern:
However, the rule never triggers. When I inspect the raw event in CloudWatch Logs, the detail-type field is actually routing.interaction.created. Is there a list of valid detail-type values for GC events? I cannot find this in the standard API docs. Also, the source seems to vary between com.genesis.platform and com.genesis.routing. I am trying to capture all new interactions for our downstream processing service. My current rule is too broad or too narrow. How do I structure the pattern to catch these reliably without missing events? I need to map this to our existing Five9 logic where we filtered by specific IVR paths. Thanks for the help.
Have you tried adjusting the source identifier? The default com.genesis.platform often misses specific interaction payloads. In my Laravel setup, I use these steps:
How I usually solve this is by validating the payload structure first. The suggestion above is correct: com.genesis is a typo. Use com.genesys.platform. My SvelteKit proxy confirms detail.eventType is the key. I poll /api/v2/events/presence to verify the stream before relying on EventBridge filters.
I typically get around this by validating the payload structure first. The suggestion above is correct: com.genesis is a typo. Use com.genesys.platform.
My SvelteKit proxy confirms detail.eventType is the key. I poll /api/v2/events/presence to verify the stream before relying on EventBridge filters.
This ensures the event pattern matches the actual schema. Check your CloudWatch logs for unmatched events to debug further.