Hey folks,
We’re trying to clean up our Architect setup by pulling a chunk of verification logic into a single “Common Module” flow. The idea is to have five different inbound call flows trigger this one shared flow, run the checks, and then return control to the caller.
I know how to do this visually in Architect by dropping a “Run Flow” action. The problem is we’re managing our flows via the CXone API (or at least trying to automate the updates) and I can’t find the right JSON structure to link an existing flow as a sub-flow action.
I’m looking at the /api/v2/architect/flows endpoint. When I POST a new flow, the actions array is where I’d expect to define this. But the docs are pretty light on how to reference another flow by ID within an action definition.
Here’s the snippet I’m throwing together based on some guesswork:
{
"id": "my-main-inbound-flow",
"name": "Main Inbound",
"type": "call",
"actions": [
{
"id": "trigger-common-module",
"type": "RunFlow",
"settings": {
"flowId": "abc-123-common-module-id",
"returnAction": "post-check-action"
}
},
{
"id": "post-check-action",
"type": "PlayPrompt",
"settings": {
"promptId": "thanks-for-calling"
}
}
]
}
When I hit the API with this, I get a 400 Bad Request. The error message just says Invalid action configuration which isn’t super helpful.
Is RunFlow even a valid action type in the API schema? Or do I need to use Transfer or something else? If it’s not supported via the API, is the only way to maintain this modularity by manually editing in the UI?
We’re on the latest CXone patch level, by the way. Just want to avoid hardcoding the logic five times if we can help it.