Accessing Web Messaging Participant Attributes in Architect Data Action

We are trying to pull participant attributes from Web Messaging into our inbound message flow. The goal is to route based on user tier. I added a REST Data Action to fetch the interaction details, but the response payload doesn’t include the attributes we set via the widget. Here is the endpoint we are calling:

GET /api/v2/interactions/participants/{participantId}

The response returns basic info but no custom attributes. How do we access those specific fields in the flow?

The participant endpoint you’re hitting returns the platform-level metadata. Custom attributes from the widget live on the interaction object itself, not the participant record. You need to query the interaction ID instead.

Use the interaction ID from the current context. The endpoint is GET /api/v2/interactions/{interactionId}. The response includes a channelType and a customData object. That’s where your widget attributes show up.

Here is the Architect Data Action config:

{
 "method": "GET",
 "url": "/api/v2/interactions/{interactionId}",
 "headers": {
 "Authorization": "Bearer {access_token}"
 }
}

Map the response body to a variable. Then access the attribute via response.customData.yourAttributeKey. If you’re using the DFO API directly in code, the path is similar but you might need to expand the customData field explicitly depending on the SDK version. In Architect, it’s usually there by default.

Check the interaction type. If it’s webchat, the attributes are in customData. If it’s webchat-v2 or a custom channel, the structure might differ slightly. Look for attributes or context in the response root.