Output node
SQLite File
Write the incoming rows into a table in a new SQLite database file.
What it does
Writes the incoming rows into a table inside a brand-new SQLite database file, which you download from the run afterwards. SQLite is a whole database in a single file, so whoever receives it can run SQL against it without installing anything. A fresh file is created every run, so there is no append or overwrite mode to choose.
Inputs and outputs
| Inputs | One. |
| Outputs | None. This node ends a pipeline. |
When to use it
- Hand someone a queryable database instead of a flat file
- Ship a portable extract that keeps its table structure
- Give a colleague something they can open in any SQLite tool and query
Examples
Write a table
File: customers.db · Table: customers
The whole result lands in one table inside a new file.
What the recipient can do
SELECT * FROM orders WHERE status = 'paid'
The point of shipping a database rather than a flat file.
Dates stay usable
2026-03-01 → TEXT '2026-03-01'
SQLite's own date() and datetime() functions read this form.
Tips
- Find the file on the run's detail page once the run finishes.
- A Test run leaves you nothing to download; press Run for a real file.
- A brand-new database file is created each run: there is nothing to append to and nothing to overwrite.
- Dates and decimals are stored as text, because SQLite has no date or decimal type. It's ISO 8601 text, which SQLite's own date() and datetime() functions read, and text is what keeps a decimal exact instead of rounding it to a float.
- The table name can't be blank; the run stops and names the node if it is.