I’m building a custom data action in Architect to fetch user profile data from a NICE Cognigy instance. The goal is to retrieve specific tokens and map them to Architect variables for use downstream in the flow. I’ve set up a simple HTTP GET request to the Cognigy API endpoint, which returns a JSON payload containing the user’s preferences.
The issue arises during the mapping step. When I try to assign the value of profile.preferences.theme to an Architect variable, the data action fails with a generic “JSON parsing error” in the logs. The response from Cognigy looks perfectly valid when I test it in Postman:
{
"status": "success",
"data": {
"userId": "12345",
"preferences": {
"theme": "dark",
"language": "en"
}
}
}
I’ve tried using both $.data.preferences.theme and data.preferences.theme in the mapping JSON path, but neither works. The error log just says Invalid JSON path without pointing to the specific field. I’ve also verified that the response body is being passed correctly from the HTTP step to the mapping step by logging the raw response body, which matches the payload above.
Has anyone encountered this specific parsing issue with nested JSON objects in Architect data actions? I’m wondering if there’s a known limitation with how Architect handles deeply nested properties or if I’m missing a configuration step in the HTTP request settings.