MySQL
Read, write, insert/upsert records, and create-table-if-not-exists against MySQL and MariaDB, with ?-bound parameters and double-brace {{$.path}} mustache tokens pulled from the flow. Node/TypeScript sibling of the Go Postgres plugin.
- SDK
- Node
- Protocol
inflowv1- Actions
- 4
- Version
- v0.1.0
- Author
- Inflowenger
- Runs on
- Any
inflowv1host - Categories
- Databases and stores
Reach for it when
MySQL or MariaDB — the same four actions as the Postgres plugin, with ? binding.
The use people don't expect
Usually the oldest thing in the estate and the one nobody wants to touch. It joins the graph as a node under its own credential and nothing has to be migrated first.
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.
Reading the 2011 database without a migration project
Starts withA process that needs data only the legacy app has.
- MYSQL
Reads the rows, with
{{$.path}}tokens filling the filter from upstream. - Code
Normalises the column names somebody chose fifteen years ago.
- POSTGRES
Writes the shape the rest of the flow wants.
What you getThe integration is one node and one credential instead of a replatforming proposal. The legacy app keeps running, unaware.
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.