Got another one of these - Architect flow’s trying to POST to a data action and it’s choking on the payload. PureCloudPlatformClientV2 is building the JSON just fine, but the API keeps returning a 400 Bad Request with “Invalid payload format” in the response body. It’s happening on POST /api/v2/dataactions/{dataActionId}/executions.
The flow’s doing a simple string concatenation to build the request body - nothing fancy - and passing it through the SDK’s dataAction.execute() method. We’re on SDK version 14.2.0, and it’s consistently failing. @genesys/cloud-node- handles the request serialization, and I suspect it’s adding something unexpected to the payload, but I can’t put my finger on it.
It feels like a schema mismatch, but the data action’s input schema should accept a string. The validator isn’t even getting far enough to look at the schema; it’s rejecting the request before it hits the validation pipeline. The data action’s just a basic HTTP GET request - we’re trying to pass a URL as a string, and it’s like it’s expecting an object instead.
{
"url": "https://example.com/api/data"
}
It’s baffling because the same payload works perfectly fine when tested directly with Postman.
The flow’s doing a simple string concatenation to build the request body - nothing fancy - and passing it through the SDK’s dataAction.e
String concat’s the issue. Stop doing that. PureCloud’s API’s are real picky about JSON. It isn’t just teh string format.
PureCloudPlatformClientV2 is building the JSON just fine
That’s…not what’s happening then. SDK’s don’t magically fix broken JSON. It’s likely you’re serializing something incorrectly before it gets to the SDK.
Try this. Don’t build the string. Build a proper JSON object in your flow, then serialize that. It took like 2 hrs to debug something similar last week, and it was this.
{
"param1": "value1",
"param2": 123,
"param3": true
}
Then, use the SDK to send that object. Don’t even think about manually constructing strings. It’s a waste of time. Also, double-check the data action definition. Mismatched types there will cause problems. The API errors are not always helpful.
W.
hey! yeah that string concat thing is super finicky - it’s probably adding extra quotes or something weird.
Cause: The API expects valid JSON, and string concatenation often creates invalid JSON - especially with nested objects. Is the SDK even trying to serialize the string into JSON first?
Solution: Try building a proper JSON object in the flow, then using the SDK to serialize it. Something like this (though I’m not a JSON expert lol):
{
"key1": "value1",
"key2": "value2"
}
Then pass that to the data action, not just a string.