I’m trying to set up an EventBridge rule to catch Genesys Cloud conversation events, specifically when a conversation starts. I’ve created the rule in AWS and linked it to a Lambda function, but the Lambda never gets invoked even though conversations are clearly happening in the queue. I’m pretty sure the event pattern JSON is the problem, but I can’t figure out what’s wrong with it.
Here’s the pattern I’m using:
{
"source": ["com.genesys.cloud"],
"detail-type": ["Conversation Event"],
"detail": {
"eventType": ["conversation.created"]
}
}
I’ve double-checked the source and detail-type values against the Genesys Cloud documentation, and they look correct. The Lambda function itself works fine when I test it with a manual invocation, so the issue isn’t there. I’ve also verified that the EventBridge bus is receiving events from Genesys Cloud by checking the CloudWatch logs, but the specific rule just doesn’t seem to match anything.
Is there something I’m missing in the event pattern? I’ve tried adding more fields to the detail object, like the conversation ID or channel type, but that just makes things worse. The rule should be simple enough to catch all conversation.created events, but it’s not working.
I’m using the standard Genesys Cloud EventBridge integration, and I’ve followed the setup guide to the letter. The OAuth token is valid, and the permissions are set correctly for the EventBridge rule to invoke the Lambda. It’s just the pattern matching that seems to be the bottleneck.
Has anyone else run into this issue? I’m stuck and can’t move forward with the automation logic until I can get these events triggering properly. The documentation isn’t very clear on what specific fields are required for the pattern to match, so I’m guessing here.