Hey everyone, what’s the best way to ensure the full conversation metadata is hitting the event bus when a flow ends?
The setup is pretty standard. Using an EventBridge integration to catch flow events and pushing them into a Lambda for processing. It’s all defined in our CloudFormation stack to keep the IAM roles tight. Everything works for the initial trigger, but the payload coming through is stripped. It’s basically doing jack all when it comes to the actual variables set in Architect.
Checked a few community posts about webhook timeouts, but the latency on the AWS side is low. The EventBridge target is active and the integration is green. Here’s the snippet of the event we’re seeing in the CloudWatch logs:
{
"version": "0",
"id": "evt-12345-67890",
"detail-type": "flow.completed",
"source": "genesyscloud.events",
"time": "2023-10-27T14:20:00Z",
"detail": {
"conversationId": "a1b2c3d4-e5f6-7890",
"flowId": "f9876543-210b-cde",
"outcome": "success"
}
}
The detail object is missing the custom attributes. We’ve tried updating the webhook via POST /api/v2/integrations/webhooks/{tokenId}/events to see if a manual trigger helps, but the response is the same. Is there a specific setting in the Architect flow itself that needs to be toggled to “export” these variables to the event bus?