Data Action returns undefined despite 200 OK — JSON path mapping issue

Architect & Flows
1

We’ve got a custom Data Action calling an internal service to enrich interaction data, but the success output is coming back as undefined even though the HTTP response is a clean 200 OK. The payload structure is straightforward, yet the field mapping in Architect seems to be ignoring it. We’re using the standard HTTP GET action, and the response body contains a single object with a score property. I’ve verified the endpoint directly via Postman, and it returns {"score": 85} consistently. The issue appears to be in how the Data Action parses the response body into the output fields for the flow.

Here’s the JSON mapping configuration we’re using in the Data Action definition:

{
 "outputMapping": {
 "riskScore": ".score"
 }
}

In the flow, when we try to use riskScore in a subsequent condition, it evaluates to undefined. I’ve tried changing the path to $.score and even wrapping it in an array notation like [0].score, but nothing sticks. The logs show the response body is correctly received, but the transformation step seems to fail silently. We’re using the latest version of the Architect UI, and there are no validation errors on the Data Action itself. Has anyone hit a similar issue where the JSON path resolution fails for simple root-level properties? We need this value to route the call correctly, and right now it’s defaulting to the fallback path because the variable is empty.

2

Studio Data Actions don’t parse JSON automatically like Architect does. You’re getting the raw string back.

You need to add a JSON.parse step or handle it in the script logic before passing it to the output. If you’re using a custom script action, the response body is a string.

// In your Studio script action
const response = await actions.http.request({
 method: 'GET',
 url: 'https://your-internal-service/enrich'
});

// Parse the string body
const data = JSON.parse(response.body);

// Set the output correctly
return {
 score: data.score
};

If you’re stuck in the visual builder without a custom script, chain a “Set Variable” action. Use the expression {{action.response.body}} and then parse it? No, Studio doesn’t have a native JSON parser action exposed easily in the flow canvas for simple types without a script.

Best bet: wrap that HTTP call in a small ES6 script action. It’s cleaner anyway. You’ll save yourself headaches when the payload gets deeper.