We are integrating NICE Cognigy profile tokens into Genesys Cloud via a Data Action. The HTTP call to the Cognigy API returns a 200 OK with valid JSON, yet the Data Action consistently throws a JSON parsing error during the response mapping phase. The payload contains nested objects for user attributes. We suspect the issue lies in how the response body is being interpreted by the Genesys engine. Here is the raw response snippet causing the failure. Does anyone have experience mapping complex JSON from external APIs in Data Actions?