Postgres
Read, write, and create-table-if-not-exists against PostgreSQL, with $1-bound parameters and double-brace $.path mustache tokens pulled from the flow.
- SDK
- Go
- Protocol
inflowv1- Actions
- 3
- Version
- v0.1.0
- Author
- FloMorphic
- Runs on
- Any
inflowv1host - Categories
- Databases and stores
Reach for it when
The flow's own system of record — state that outlives any single run.
The use people don't expect
The quiet workhorse. Most flows that do something interesting have a POSTGRES node early (read the context) and late (write what happened), and the middle is the part people photograph.
A flow that uses it
Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.
Case management on top of a flow
Starts withRecords arrive — a webhook, a file drop, a sweep.
- POSTGRES
Create-table-if-not-exists on first run, so the flow carries its own schema.
- Contract
Decides whether this record is a case somebody has to act on.
- POSTGRES
Opens the case, parameterised with
$1-bound values from the flow. - Human in the Loop
Someone works it. The flow waits — days is fine.
- POSTGRES
Closes it, with who decided and when.
What you getThe audit trail is a side effect of the process rather than a reporting project. The run record and the table agree because they were written by the same run.
The reference, not the pitch
This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.
Near it in the catalog
Many rows, asked questions repeatedly — events, logs, metrics, anything you'll want a GROUP BY over.
DUCKDBDuckDBThe data is files — CSV, Parquet, JSON, Excel — on disk, over https, or in a bucket. SQL over them in place.
MSSQLMicrosoft SQL ServerSQL Server or Azure SQL — including the branch instance that legally cannot leave the building.