We’re trying to route web chat interactions based on custom attributes set via the Web Messaging SDK, but those attributes aren’t showing up in the Architect inbound message flow.
On the client side, we’re setting attributes like this before sending the message:
const gc = window.GenesysCloud;
gc.setParticipantAttributes({
'priority': 'high',
'source_channel': 'web'
});
In Architect, I’ve added a Data Action to fetch the participant details using the /api/v2/conversations/messages/participants/{participantId} endpoint. The response comes back with a 200 OK, but the attributes field is completely empty. Here’s the JSON snippet from the response:
{
"id": "abc123",
"externalId": "def456",
"attributes": {
"system:participantId": "abc123"
}
}
The custom attributes we set via the SDK are nowhere to be found. I’ve tried checking the initialAttributes field as well, but that’s also empty. We’ve confirmed these attributes are being sent correctly by checking the network tab in the browser dev tools.
Is there a specific flag or configuration needed to make participant attributes from Web Messaging visible in the Architect flow? Or is this a known limitation with the current API version?
We’re using the latest version of the Web Messaging SDK and have double-checked that the integration is properly configured in the Genesys Cloud UI. Any help would be appreciated.