Running into a wall with a Data Action that queries the NICE Cognigy API for profile tokens. The HTTP request itself looks fine-I’m getting a 200 OK back from the external endpoint. But Genesys Cloud keeps failing the mapping step with a generic ‘Invalid JSON’ error in the debug logs.
Here’s the payload coming back from Cognigy:
{
"token": "abc123xyz",
"expires_in": 3600,
"user_id": "u-998877"
}
And here is the JSON mapping I’m using in the Data Action:
{
"mapping": {
"token": ".token",
"expiration": ".expires_in"
}
}
I’ve tried wrapping the values in quotes, changing the delimiter, and even echoing the raw body to a log to confirm it’s valid. The raw body definitely parses in a JSON linter. Is there a hidden character issue with the Cognigy response that Genesys isn’t handling? Or am I missing a step in the Data Action configuration to handle external JSON bodies properly? The error doesn’t give much context beyond the parse failure.