Flowintent / proof
Loading docs
Understand how workflow records preserve visual design, generated source, route context, run history, and evidence pointers.
A workflow record is the durable unit of quantum work. It owns the visual design, generated source, route context, run history, comments, and evidence references.
Use this reference when an integration needs to import, duplicate, clone, or review a workflow without confusing private workspace state with public proof.
This page belongs to the API & Evidence section and should be read with the related pages listed at the end.
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
Workflow endpoints are session-authenticated and operate on the caller's own records. They serve the signed-in product UI and scripts that reuse a browser session.
GET /api/workflows?search={q}&limit={n} List your workflowsPOST /api/workflows Create a workflow recordGET /api/workflows/{id} Fetch one workflow recordPUT /api/workflows/{id} Update the record (only provided fields change)PATCH /api/workflows/{id} Alias of PUT (same partial update)DELETE /api/workflows/{id} Delete a workflowPOST /api/workflows/{id}/duplicate Duplicate into a new owner-scoped record
A workflow record includes name, owner, workspace, visual operations, layout, qubit and classical-bit counts, revision, share and template flags, tags, and timestamps. Generated source is derived from the operations on demand.
Generated source can change when the visual circuit changes. Treat source snapshots used for a run as evidence artifacts rather than mutable draft text.
{"name": "Bell state baseline","qubits": 2,"classicalBits": 2,"operations": [{ "id": "op-1", "gate": "H", "targets": [0] },{ "id": "op-2", "gate": "CNOT", "targets": [1], "controls": [0] },{ "id": "op-3", "gate": "MEASURE", "targets": [0, 1], "classicalTargets": [0, 1] }],"tags": ["tutorial"]}
{"workflow": {"id": "cmbw1f2k80001abcd1234efgh","userId": "cmbvzx9aa0000abcd9012mnop","workspaceId": null,"name": "Bell state baseline","description": null,"qubits": 2,"classicalBits": 2,"revision": 1,"operations": [{ "id": "op-1", "gate": "H", "targets": [0] },{ "id": "op-2", "gate": "CNOT", "targets": [1], "controls": [0] },{ "id": "op-3", "gate": "MEASURE", "targets": [0, 1], "classicalTargets": [0, 1] }],"layout": {},"isPublic": false,"isTemplate": false,"isFavorite": false,"shareToken": null,"tags": ["tutorial"],"createdAt": "2026-06-12T09:28:00.000Z","updatedAt": "2026-06-12T09:28:00.000Z"}}
Cloning public shares or templates creates a new owner-scoped record (POST /api/workflows/{id}/duplicate). It must not carry private provider credentials, billing state, admin notes, or original user secrets.
Imports validate circuit operations before a run can be routed; generated source is re-derived from those operations rather than imported as text.
Learn the product language behind workflows, blocks, generated code, provider routing, runs, evidence, and learning records.
Review generated Qiskit, Cirq, and OpenQASM output beside the visual workflow before routing or exporting.
Understand the public product contract for creating, tracking, exporting, and reviewing quantum workflow runs.