Flows

A flow is a graph of nodes that drives a call's conversation. You author graphs in the dashboard editor; at publish time the graph is compiled and frozen into a runtime artifact (objective, outcome_schema, tools). Runtime reads the frozen columns only — editing a graph never silently changes the behavior of in-flight or published flows.

States

• Draft — editable. Saved as graph_json on the flow row.
• Published — compiled artifact written to published_compiled_*. Live calls use this. Editing a draft after publish has no effect until you re-publish.

Endpoints

• GET /v1/flows — list flows (all states).
• POST /v1/flows — create a new draft.
• POST /v1/flows/{flow_id}/preview — dry-run the compile (no persistence).
• POST /v1/flows/{flow_id}/publish — compile and freeze.

Node types today

OpenPhn ships a handful of node types (message, question, branch, etc.) and seeds five starter templates. Snippet / custom-tool nodes are not yet supported — the compiler rejects them. Template-based graphs cover the common cases; reach out if you need something bespoke.

Attaching a flow to a number

Set flow_id on the number via PATCH /v1/numbers/{number_id}. Inbound calls to that number run the attached flow.