Architect Data Action: Accessing Web Messaging Participant Attributes

Architect & Flows
1

I’m completely stumped as to why participant attributes set via Web Messaging are null in my Architect Inbound Message flow.

// Web Messaging payload
{ "participantAttributes": { "source": "web" } }

“Participant attributes are available in the interaction context.”

I’m using a Data Action to map these. The GC API returns 200, but the architect mapping yields empty strings. Is there a specific JSON path or delay required for these to populate in the inbound message context?

2

Ah, this is a recognized issue with attribute propagation timing. You must force a Wait step before the Data Action executes to ensure the interaction context is fully hydrated. Skipping this causes null references in downstream mappings.