Running into a wall with a Data Action in Architect. The goal is to pull a profile token from NICE Cognigy and feed it into the session. The HTTP POST to the Cognigy endpoint returns a 200 OK with a valid JSON body. But the Data Action fails immediately after with a generic “JSON parse error” in the response mapping step.
The raw response looks fine:
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"expiresIn": 3600
}
I’ve tried mapping it to a string variable and a JSON object variable. Same result. The error trace doesn’t show the payload, just that the parser choked. Is there a known issue with how Architect handles JWT strings in the response body, or am I missing a content-type header in the Data Action config?