We are implementing a validation step in our CX as Code pipeline that relies on an Architect Data Action to verify external system availability. The action calls a simple REST endpoint, but the success output variable response.body is consistently undefined when mapped in the subsequent flow node. The HTTP request itself seems fine, returning a 200 status code with the expected JSON payload.
The configuration for the Data Action looks like this:
{
"httpRequest": {
"url": "https://api.internal/health",
"method": "GET",
"headers": {
"Authorization": "Bearer {{authToken}}"
}
},
"responseMapping": {
"statusCode": "response.status",
"body": "response.body"
}
}
The debug logs show the raw response contains {"status": "ok", "version": "1.2"}. I have tried mapping it explicitly to response.body.status and even wrapping it in a JSON.parse call within the expression, but the variable remains empty in the flow context. Is there a specific syntax required for mapping the body of a GET request in the Data Action definition? The documentation suggests the default mapping should handle JSON automatically, but it’s not working as expected in our environment.