Save to Database stores your workflow results in a database table on your site. It is the save output type of the Output node, and it is how you build up your own custom tables of structured data over time.
What it does
- Writes a row to a database table each time the workflow runs.
- Lets you define the table’s columns, so you can create a custom table for your data.
- Maps each column to its own upstream field, so every value lands in the right place.
Set it up
- Add an Output node and set the output type to Save.
- Choose the target table, or define a new one by adding its columns.
- Map each column to an upstream field so the run knows what to write.
Configuration reference
| Field | What it does |
|---|---|
| Selected table | The target table to write to. |
| Columns | The column definitions for the table, used when you create a custom table. |
| Field mappings | Maps each table field to a node input. |
Mapping fields
Each column maps to its own upstream field, the same rules as the Post node. Feed each column from a real named output, such as a structured field from an AI Prompt node or an AI Extract Information node. See Data flow and variables.
Custom tables
Tables you create this way are your own custom tables. You can keep writing to them across many runs to build a growing dataset, for example a log of processed submissions or a table of generated content. Manage your custom tables from the Tables page in the plugin.
Where it runs, and cost
Save to Database writes to your WordPress site, so this delivery runs on the site rather than in the cloud. The Output node itself costs 0 credits. See Local vs Cloud execution.