n8n SeaTable Node v2: “base not found in big data storage” on write operations (non-Enterprise)
Environment:
-
n8n version: 2.13.4 (Cloud)
-
SeaTable Node: v2 (n8n-nodes-base.seaTableTool, typeVersion 2)
-
SeaTable Plan: Free / Plus (not Enterprise)
-
Big Data Storage: not activated (not available on my plan)
Problem: All write operations (update row, create row) with the SeaTable Tool Node v2 fail with a 404 error:
{ "error_message": "base not found in big data storage" }
Read operations (list) work fine. Only update and create are affected.
Steps to reproduce:
-
Create a workflow with an AI Agent and SeaTable Tool Nodes (v2) as tools
-
Use
updateorcreateoperations on any table -
The node returns 404: “base not found in big data storage”
Root cause (my assumption): The v2 node uses the /api-gateway/ endpoints for all operations. These endpoints seem to require Big Data Storage to be activated in the base. Since Big Data Storage is only available on SeaTable Enterprise, the v2 node effectively breaks write operations for all non-Enterprise users.
The v1 node used /dtable-server/ endpoints which work without Big Data Storage.
Workaround attempted:
-
Downgrading to typeVersion 1 by editing the workflow JSON works for the API calls, but v1 requires columns to be explicitly defined in the node configuration. This removes the dynamic
$fromAI()capability that makes v2 so useful with AI Agents. -
Installing the SeaTable community node is not possible on n8n Cloud (not verified).
Expected behavior: The v2 node should work with bases that do not have Big Data Storage activated, by falling back to the /dtable-server/ endpoints when /api-gateway/ returns a “big data” error — or by not requiring Big Data Storage at all.
Request: Could you either:
-
Fix the v2 node to work without Big Data Storage, or
-
Get the community node (
n8n-nodes-seatable) verified for n8n Cloud so we can install it as an alternative?
Thank you!
