We’re routing web chat transcripts through an inbound message flow for compliance logging. The widget sets custom attributes like customer_tier before the message hits the queue. Inside Architect the flow only shows standard system fields. Tried pulling the data with a Get REST Proxy data action to hit /api/v2/conversations/messaging/participants but the token scope keeps blocking it. Pretty frustrating. Here is the payload coming into the flow. The custom fields are nested under participant_attributes but the expression builder doesn’t recognize the path.
{
"type": "message",
"participant_attributes": {
"customer_tier": "premium",
"order_id": "ORD-9921"
}
}
Used {{participant_attributes.customer_tier}} in a set field action but it returns null every time. The routing rules require those values for the downstream API call. How do we actually map those nested keys inside the inbound message flow without writing a full external service