Data Action JSON Parsing Error on Cognigy Profile Token Query

I’ve got an Architect flow that hits a custom DFO endpoint to pull a profile token from Cognigy. The HTTP request succeeds with a 200 OK, but the Data Action fails with a generic JSON parsing error downstream.

Here’s the response payload I’m seeing in the debug logs:

{
 "status": "success",
 "data": {
 "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
 "expires_in": 3600,
 "user_id": "12345"
 }
}

The Data Action JSON mapping is set to extract $.data.token. It works fine when the response is simple, but as soon as I add the nested data object or if the response includes extra metadata fields, it chokes. The error in Architect just says “Invalid JSON structure” without pointing to the specific field.

Is there a known limitation with how the Cognigy integration handles nested objects in the response body? Or am I missing a specific header in the Data Action config to force raw JSON parsing? I’ve tried setting the content-type to application/json explicitly, but no luck.

Here’s the Data Action config snippet:

{
 "method": "GET",
 "url": "https://api.cognigy.ai/v2/profiles/token",
 "headers": {
 "Authorization": "Bearer {{sys.auth.token}}",
 "Content-Type": "application/json"
 },
 "mapping": {
 "token": "$.data.token"
 }
}

It feels like the parser is expecting a flat key-value pair instead of an object hierarchy. Any ideas?