I’m trying to grab custom attributes from a Web Messaging session inside an Architect Inbound Message flow. The data action calls an external endpoint, but the Participant Attributes context variable returns null for my custom keys like user_segment. Here’s the mapping JSON I’m using:
"inputs": { "segment": "{{Participant Attributes.user_segment}}" }
The attribute is definitely set in the browser console before the message sends. Am I missing a specific scope setting in the Web Messaging client config or is this a known gap in how Architect parses those custom fields?