Docs state: “The response body must be valid JSON for the Data Action to parse the result into variables.”
I’m hitting a wall with a specific integration pattern. We have a Genesys Cloud Architect flow that needs to fetch a user’s profile token from our NICE Cognigy instance before routing. The Cognigy API endpoint returns a valid JSON object, but the Genesys Data Action consistently fails with a generic Error parsing response body message, resulting in a null payload downstream.
The HTTP request configuration in the Data Action is straightforward. I’m using a simple GET request to https://my-cognigy-instance.cognigy.com/api/v1/profiles/{userId}/token. The headers include the Authorization: Bearer <token> and Content-Type: application/json.
Here is the exact JSON payload returned by the Cognigy endpoint when tested in Postman:
{
"status": "success",
"data": {
"profileToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"expiresIn": 3600
}
}
In the Genesys Data Action, I’ve mapped the response body to a variable called cognigyResponse. The error log in the interaction history shows:
Failed to parse response as JSON. Expected object or array.
I’ve verified the Content-Type header in the Data Action is set to application/json. I’ve also tried adding a JSON path filter /data in the Data Action configuration to extract just the inner object, but it still fails at the initial parse stage. The raw response body in the debug log looks identical to the Postman output. No extra whitespace, no BOM characters.
Is there a known issue with how Genesys Cloud Data Actions handle nested JSON structures from external HTTP endpoints? Or am I missing a specific header configuration that forces the parser to treat the body as a string first? The documentation is silent on nested object handling for HTTP Data Actions.