I’m trying to push some custom metadata into the conversation using the Set Participant Data action in Genesys Architect. The goal is to have these variables available downstream when the call transfers to a queue.
I’ve got the action configured to set a JSON payload like this:
{
"customData": {
"tier": "premium",
"source": "ivr_menu"
}
}
The issue is that right after the Set Participant Data action, if I use a Data Action to fetch the participant details, the custom data shows up fine. But once the flow transitions to the Transfer to Queue action, those values seem to vanish.
I checked the /api/v2/interactions/{interactionId}/participants/{participantId} endpoint via the API Explorer while the flow was running, and the customData field is null in the response.
Is there a specific way I need to structure the JSON for the Set Participant Data action? Or am I missing a step to ensure the data persists through the transfer? I’ve tried setting the merge option to true, but that didn’t change anything.
Here’s the exact JSON I’m passing to the Set Participant Data action:
{
"customData": {
"tier": "premium"
}
}
Any ideas on why it’s dropping off?