I’ve got an EventBridge rule that should trigger on genesyscloud.conversation:created events, but it’s dead silent. The API returns 200 OK when I create the rule, and the rule state is ACTIVE, yet no events hit my target Lambda. I’m using the Genesys Cloud JS SDK to manage the integration, but I suspect the issue is purely in the EventBridge event pattern JSON.
Here’s the pattern I’m sending:
{
"source": ["genesyscloud"],
"detail-type": ["Conversation Created"],
"detail": {
"type": ["conversation"],
"eventType": ["conversation:created"]
}
}
I’ve verified the detail-type matches the CloudWatch Logs output for test events. The source is correct. I’m using the standard Genesys Cloud event source ARN. No errors in the rule history. Just nothing.
- Environment: Genesys Cloud Org ID
abc123, AWS Regionus-east-1 - SDK:
genesys-cloud-nodev5.2.1 - Rule State: ACTIVE
- Target: Lambda function with basic permissions
- Test Event: Manually triggered a
conversation:createdvia API - CloudWatch: Shows the event was published to EventBridge
- Rule History: Empty
I’ve tried simplifying the pattern to just source and detail-type, but still no luck. I’ve checked the IAM role for the Lambda, and it has eventbridge:Invoke permissions. The rule’s event-bus-name is default. I’m using the createEventBridgeRule method from the SDK, which seems to work fine for other event types like user:updated.
Any ideas on what I’m missing? The pattern looks right to me.