The outbound Data Action keeps throwing a 500 error when trying to map a nested JSON response from our internal service to Architect variables. The external API returns a standard 200, but the mapping logic seems to choke on the object depth. Here is the Data Action config:
{
"method": "POST",
"url": "https://internal-api.example.com/check",
"body": "{{contact.attributes.input}}",
"responseMapping": {
"contact.attributes.status": "$.result.status",
"contact.attributes.details": "$.result.details.info"
}
}
The response payload looks like this:
{
"result": {
"status": "OK",
"details": {
"info": "Verified"
}
}
}
I’ve checked the following:
- The external endpoint is reachable from the Genesys Cloud environment (verified via curl from a test server in the same region).
- The JSON path syntax matches the official documentation for JMESPath or simple dot notation.
- The variable
contact.attributes.detailsexists in the flow context. - Swapping the nested path for a flat field works fine, so it’s specifically the nesting causing the issue.
Is there a limit on how deep the response mapping can go? Or is there a specific syntax I’m missing for nested objects?