Update an extraction flow
Partially update an extraction flow. Common uses are switching the publish mode and editing the DAG (adding, modifying or removing nodes).
Publish modes:
auto_publish— Each successful flow run automatically publishes the extracted data. No separate publish step is required.manual_publish— Flow runs only compute and persist extracted data in the warehouse. Publishing to downstream indexes must be triggered explicitly via thepublishaction. Use this when you want to review the results of a run before exposing them to search / agents.
Editing the DAG: Send the full updated dag object — the backend
replaces the stored DAG on every PATCH. There is no node-level patch
endpoint. When removing a node, also strip its name from any downstream
depends_on arrays. inputs and outputs may be sent empty; the
backend resolves them automatically.
Authorizations
Use Authorization: Bearer
Path Parameters
UUID of the project
UUID of the extraction flow
Body
Human-readable name of the flow
Controls whether extracted data is pushed to downstream indexes
automatically after each run (auto_publish) or only on an
explicit publish call (manual_publish).
auto_publish, manual_publish DAG describing the extractor pipeline. PATCH replaces the stored DAG verbatim — there is no node-level patch endpoint.
Response
Flow updated successfully
auto_publish— runs automatically push extracted data to downstream indexes.manual_publish— publishing is triggered explicitly via thepublishaction.
auto_publish, manual_publish DAG describing the extractor pipeline. PATCH replaces the stored DAG verbatim — there is no node-level patch endpoint.
Per-namespace-type TurboPuffer namespace mapping populated on publish.