SQLiteInstall

Summary

Insert each input item into a SQLite table, or update the existing row when its configured match columns conflict. Select the database using the credential path, a file inside the credential’s base directory, or an absolute path override.

Inputs

• Database File Path Override — Optional absolute database file path; takes precedence over the credential path and base directory.
• Database — Optional database file path relative to the credential’s base directory. It is ignored when an override is set.
• Read Only — Defaults to false. When enabled, SQLite rejects writes, including this operation.
• Confirm Destructive Operation — Defaults to false. Controls the guard for whole-table deletes or updates and drop/truncate statements; ordinary upserts use an insert conflict clause.
• Execution Mode — Defaults to Independent, running one statement per input item. Transaction runs items in one transaction and rolls back on an error. Multi-Row Insert is insert-only and does not apply to this operation.
• Table (required) — SQLite table to write to; choose from the list or enter its name.
• Columns — Columns to insert. If empty, uses the fields from each input item. For this operation, columns not listed in Match Columns are updated on conflict.
• Match Columns (required) — Columns defining the conflict target. Their values are read from each input item. The table must have a matching SQLite constraint for the upsert conflict target.

Output shape

A list of output items, generally one per input item, each containing changes and lastInsertRowid.

lastInsertRowid is a number when safely representable, otherwise a string. If all selected columns are match columns, a conflict does nothing. With Continue On Fail, errors are returned as items containing an error field; transaction mode rolls back on an item error.

Links

• n8n community nodes installation guide