Data Table Node
Built-in persistent data storage for workflows on indie.money
Written By Philippe
Last updated 39 minutes ago
Data Table Node
✅ Supported — all row and table operations work as in n8n. Tables are shared by the workflows of one Builder, and never by two Builders (see Scope).
Compatibility
Usage
Use this node to store and retrieve structured data within your workflows. Data persists across runs.
Scope
Data tables are shared per Builder. Every workflow from the same Builder uses the same tables. This is different from n8n, where all workflows in a project share the same tables.
- Workflows from the same Builder share tables. A table name used by two of them points to the same table.
- Workflows from two different Builders never share tables, even when the table names match.
- 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.
- Tables stay with your account when you sell a workflow. The new owner uses their own tables for workflows from that Builder.
To ship a new version that keeps reading the same tables, see Upgrade a Workflow in Place.
A sub-workflow called with Execute Workflow uses the tables of the workflow that calls it. To share data with a workflow from another Builder, keep the table in one workflow with a Webhook trigger. The other workflow then sends or requests data with an HTTP Request node.
Storage limits
Your account gets 1 GB of Data Table storage. The limit covers all the data tables your account uses, across every workflow and every Builder.
n8n limits all data tables in an instance to 200 MiB combined, shared across every project and workflow on it (captured 2026-09-11).
indie.money checks your usage once a day, at 04:17 UTC. Table writes never fail because of storage, so usage can pass 1 GB between checks. The check then acts in two steps:
At 90% (900 MB): we warn you. The Run console and the workflow's Data tables tab show Nearly full. At 1 GB, workflows that read or write rows in your data tables pause.
At 1 GB: every workflow that reads or writes rows in your data tables pauses. A workflow that only creates or lists tables is not tracked. The Run console and the workflow's Data tables tab show Full. A paused workflow refuses runs with this message:
Paused: your data tables are full (1 GB per account). Delete a table, then turn this workflow back on.
To resume, delete a table to free space. Then turn each paused workflow back on by hand. While your account is still at 1 GB, turning a workflow back on is refused:
Your data tables are still full. Delete a table, then try again.
Sizes update about a minute after a delete. Delete a table from the workflow's Data tables tab, or from the Data tables section of the Run console. Type the table name to confirm.
A Builder you no longer run workflows from still counts toward your 1 GB. Its tables stay in the Run console under Data tables, where you can open them and delete them.
Was this helpful?
More in Data Transformation
Aggregate NodeCompare DatasetsCrypto NodeDate & Time NodeStill need help? Ask the team