I’m hitting a wall with a Data Action that calls our NICE CXone endpoint to fetch a Cognigy profile token. The GET request hits the /api/v2/interactions/{id}/profiles endpoint and returns a 200 OK, but the payload structure is tripping up the Genesys Cloud parser.
The response body looks like this:
{
"data": {
"profileToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"expiresAt": "2023-10-27T10:00:00Z"
}
}
I’ve mapped the Data Action output to data.profileToken, but the flow fails with Error: Unable to parse JSON response. If I map it to just profileToken, it comes back as null. I’ve tried adding a JSONata expression in the Data Action configuration to flatten the response, but the validation step rejects the syntax.
Has anyone successfully parsed nested JSON from an external CXone profile service into a Genesys variable? I’m starting to think the issue might be with how the Content-Type header is handled during the internal handoff, but I can’t find any docs on that.