We’ve been trying to standardize our inbound routing by pointing five separate call flows to a single Common Module for authentication. The admin UI handles the drag-and-drop perfectly, so the configuration is valid on the backend. The goal here is to push these updates via the API to keep our deployment scripts in sync.
The flow definition works locally until we add the triggerFlow action. The server returns a 400 Bad Request on the PUT to /api/v2/architect/flows/{id}. The response body points to a validation error on the settings object inside the action definition.
Attempts to swap flowId for flowRef didn’t help. Removing the wait flag just shifts the error to flowId being missing. Payload looks solid to us. Checked the schema validator twice. Nothing came back.
{
"name": "AuthCheck",
"type": "triggerFlow",
"settings": {
"flowId": "8a9b7c6d-1234-5678-90ab-cdef12345678",
"wait": "true"
}
}
The flow ID exists and is published. Nothing in the docs clarifies the exact structure required for a Common Module trigger versus a standard flow.