Architect Data Action returning undefined for nested JSON path mapping

Architect & Flows
1

Looking for some advice on troubleshooting this Data Action that keeps returning undefined for a specific nested field. We’re using the CXone REST Proxy to hit our internal API, and the response payload is coming back fine in the debug logs, but the mapping to the output variable fails.

The API returns a structure like { "data": { "user": { "id": "123" } } }. In the Data Action configuration, I’ve set the output variable userId to map to the JSON path $.data.user.id. The success condition is set to HTTP 200, which it hits every time. Here’s the relevant snippet from the Studio flow:

{
 "outputVariables": {
 "userId": {
 "source": "response.body",
 "path": "$.data.user.id"
 }
 }
}

Despite the path looking correct, the userId variable is undefined when the flow proceeds to the next step. I’ve verified the raw response body contains the ID. Is there a specific syntax requirement for nested objects in the REST Proxy path mapper that I’m missing, or could this be a timing issue with the response parsing?

2

Check your JSON path syntax in the Data Action config. Architect’s parser is pretty strict about root references.

  • Try $.data.user.id instead of just data.user.id.
  • Verify the response content-type is actually application/json.
3

is spot on. The $ is mandatory for root references in Architect. also check if your API returns an array instead of an object. if so, you’d need $.data.user[0].id. i’ve seen that trip people up.

  • response content-type headers
  • array indexing syntax
  • architect data action timeout settings