Does anyone know why my outbound data action keeps throwing a 500 error when trying to map a deeply nested JSON response?
I’ve been working on a Vue 3 dashboard that triggers an Architect flow to fetch real-time supervisor stats from our internal API. The flow uses an outbound data action to call our legacy REST endpoint. The HTTP call itself succeeds (200 OK), but the mapping step seems to choke on the response structure.
Here is the JSON payload returned by the external API:
{
"status": "success",
"data": {
"supervisor": {
"id": 12345,
"metrics": {
"active_calls": 5,
"queue_depth": 12
}
}
}
}
In the Architect data action configuration, I’m trying to map the values to flow variables. I’ve tried using the standard dot notation in the mapping field:
- Variable:
activeCalls→ Mapping:data.supervisor.metrics.active_calls - Variable:
queueDepth→ Mapping:data.supervisor.metrics.queue_depth
The documentation suggests this should work for nested objects, but the flow execution log shows a generic “Data Action Execution Failed” with a 500 status code. No detailed error message is returned in the webhook callback, which is frustrating.
I’ve verified that the variables exist in the flow context and are of the correct type (Integer). I also tried flattening the JSON response on the API side to just { "active_calls": 5, "queue_depth": 12 } and mapping directly to active_calls and queue_depth, which worked fine. So it seems to be an issue with how Architect handles nested paths in the mapping configuration.
Is there a known limitation with nested mapping in data actions? Or am I missing a syntax requirement for accessing nested properties? I’m using the latest version of the platform, and this is blocking my dashboard’s real-time update feature.