Data Table Node

Data Table Node

✅ Supported — all row and table operations work as in n8n. Tables are not shared between workflows (see Scope).

Compatibility

Usage

Use this node to store and retrieve structured data within your workflows. Data persists across runs.

Scope

Each deployed workflow has its own data tables. This is different from n8n, where all workflows in a project share the same tables.

• Two workflows that use a table with the same name each get a separate table. One workflow cannot read rows that the other wrote.
• Each person who buys your workflow gets their own empty tables. They never see your rows, and you never see theirs.
• Rows from your n8n tables are not copied when you import a workflow. A table that the workflow references starts empty.

A sub-workflow called with Execute Workflow uses the tables of the workflow that calls it. To share data between workflows, keep the table in one workflow with a Webhook trigger. The other workflows then send or request data with an HTTP Request node.

Storage limits

Each deployed workflow gets 500 MB of Data Table storage, and the limit applies per deployed workflow — every workflow you deploy gets its own 500 MB, independent of the others.

n8n limits all data tables in an instance to 200 MiB combined, shared across every project and workflow on it (captured 2026-09-11). So the gap is about 2.4x on a single workflow, and it widens with every workflow you add, because their pot does not grow and yours does: ten workflows is 5 GB here against the same 200 MiB there.

When a workflow reaches its limit, write operations (creating tables, adding columns, inserting or updating rows) stop with the error Data table storage limit reached for this workflow. Reads and deletes keep working — delete rows or tables to free space, then writes resume.