We are configuring an Architect flow to parse a response from an external API using a Data Action. The goal is to extract a specific identifier from the payload for downstream routing logic. The Data Action is set to POST to an internal service, and the response structure is documented as follows:
{
"status": "success",
"data": {
"customer_id": "12345",
"segment": "premium"
}
}
In the Data Action configuration, we have defined the success output mapping. The documentation suggests using dot notation for nested paths. We configured the output variable parsed_customer_id with the path data.customer_id. However, when the flow executes and the Data Action returns a 200 OK, the parsed_customer_id variable is consistently undefined. The debug logs show the full JSON payload was received correctly by the platform, but the extraction fails silently.
We have tried alternative paths such as $.data.customer_id and [data][customer_id], but the result remains the same. The error handling branch is not triggered because the HTTP status is 200. Is there a specific syntax requirement for nested JSON extraction in the success output mapping that differs from standard JSONPath? We are currently using the latest version of the Architect UI. The code snippet for the Data Action output configuration is below:
Output Variable: parsed_customer_id
Path: data.customer_id
Default Value: null
Any insight into why the path resolution is failing would be appreciated. We need to stabilize this before the next deployment window.