Hey everyone, I’ve run into a really strange issue with mapping nested JSON responses in a Data Action.
The Data Action calls an external endpoint https://api.internal.com/v1/status and returns 200 OK with payload {"data": {"code": 200, "msg": "ok"}}. The mapping configuration specifies "data.code" as the source for output variable responseCode. The execution logs show the HTTP request succeeds, but the variable responseCode remains null in the subsequent block.
Is the genesyscloud data action parser strictly flat, requiring explicit path traversal syntax like data->code, or is there a known issue with dot notation in the JSONPath expression?