We’re seeing a really odd behavior with a Data Action in our Architect flow. The goal is to pull a customer’s loyalty tier from an external system and pass it to the agent desktop. The Data Action is configured to call our internal API, and it returns a 200 OK with a valid JSON payload.
Here’s the response we’re getting:
{
"customerId": "12345",
"tier": "Gold",
"points": 1500
}
The Data Action maps these fields to output variables customerId, tier, and points. In the Architect flow, the Data Action succeeds, and the status is green. However, when I try to use the tier variable in a subsequent Assign step, it comes back as undefined. I’ve checked the JSON path mapping in the Data Action config, and it looks correct. I’m using the standard mapping syntax like $.tier.
I’ve tried restarting the flow and even re-saving the Data Action, but the issue persists. The customerId variable works fine, but tier and points are always undefined. Is there a known issue with how Architect handles nested or specific JSON paths in Data Action outputs? Or am I missing something in the mapping syntax? Any help would be appreciated.