Allow setting per-project upper bound on Data Tables size. Currently, only a global limit can be set via N8N_DATA_TABLES_MAX_SIZE_BYTES.
My use case:
An enterprise self-hosted environment with per-team projects.
I think it would be beneficial to add this because:
We’d like to allow our teams to benefit from Data Tables in their workflows. Currently only the global limit is available. This means, that one team can use the whole limit, leaving nothing else for the others, and there’s no way to track or prevent this.
With the proposed N8N_DATA_TABLES_PER_PROJECT_MAX_SIZE_BYTES each team would be responsible for their own budget.
Any resources to support this?
Are you willing to work on this?
Depending on my other priorities, I could contribute.
The per-project cap would be a significant improvement for multi-team deployments. The current situation where one team can exhaust the global N8N_DATA_TABLES_MAX_SIZE_BYTES is a real pain in shared instances.
As a workaround in the meantime, I’ve been routing high-volume teams to external databases (Postgres or Supabase) instead of Data Tables for their workflows, and reserving Data Tables only for small lookups. Not ideal, but it keeps the shared budget available. The N8N_DATA_TABLES_PER_PROJECT_MAX_SIZE_BYTES naming you proposed is exactly the right interface for this.