Skip to main content
First build, test, and publish your workflow. Call POST /v1/workflow-runs with workflows:run and a new Idempotency-Key for the intended run.
Replace the example UUID with your published revision UUID. An empty inputs object works only if the workflow has no required inputs. Populate it with the fields defined on Start when needed. The published revision supplies the voice, face, node instructions, tools, and subflows. Voice, face, prompt, greeting, and MCP overrides are not accepted by this endpoint. The 201 response uses the same connection fields as a voice session, plus workflow_run_id. Use the response’s id with the session status, end, and transcript endpoints. The workflow-run ID and session ID identify different resources. To release changes, publish a new revision and update the selected UUID in your application. Keep the same idempotency key and request body when retrying the same intended run.