Attempted to use Data table node but the module is disabled with the new Data table

Questions
1

Describe the problem/error/question

Hi all, the Data table is going to be a really nice feature !

I’ve just updated to 1.113.1 (and I’m running n8n on Postgres), but I get this message when I try to run a Data table node : “Attempted to use Data table node but the module is disabled”.

Information on your n8n setup

  • n8n version: 1.113.1
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue mode
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Ubuntu
2

Hi, @zlebandit
1.113.1 This is very newer version of n8n and not stable so might have some this type of issues so use older and stable version.

I hope this answer is helpful.:slightly_smiling_face:

3

Hello, can you share the workflow JSON here? and do you see the data table tab as explained here?

4

I see the data table. I can also access to the databases I created in the graphic view with a Postgres node. I tried a simple “Get Rows”.

So it seems a node issue. Perhaps a problem with de configuration of the docker-compose ? The filesystem mode ? An option to add ?

I give you my config :

n8n:
build:
context: ./n8n
dockerfile: Dockerfile
container_name: n8n
restart: always
environment:

=== CONFIGURATION RÉSEAU ===

  • N8N_HOST=${N8N_DOMAIN}
  • N8N_PORT=5678
  • N8N_PROTOCOL=https
  • WEBHOOK_URL=https://${N8N_DOMAIN}/
  • N8N_OAUTH_CALLBACK_URL=https://${N8N_DOMAIN}/rest/oauth2-credential/callback
  • N8N_PROXY_HOPS=1
  # === BASE DE DONNÉES ===
  - DB_TYPE=postgresdb
  - DB_POSTGRESDB_HOST=postgres
  - DB_POSTGRESDB_PORT=5432
  - DB_POSTGRESDB_DATABASE=n8n
  - DB_POSTGRESDB_USER=postgres
  - DB_POSTGRESDB_PASSWORD=${POSTGRES_PASSWORD}
  - DB_POSTGRESDB_CONNECTION_LIMIT=30
  - DB_POSTGRESDB_POOL_MIN=2
  - DB_POSTGRESDB_POOL_MAX=10

  # === MODE QUEUE & WORKERS ===
  - EXECUTIONS_MODE=queue
  - EXECUTIONS_PROCESS=main
  - QUEUE_BULL_REDIS_HOST=redis
  - QUEUE_BULL_REDIS_PORT=6379
  - QUEUE_HEALTH_CHECK_ACTIVE=true
  - OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true

  # === PERFORMANCE & LIMITES ===
  - NODE_ENV=production
  - NODE_OPTIONS=--max-old-space-size=4096
  - N8N_PAYLOAD_SIZE_MAX=524288000  # 500MB
  - N8N_CONCURRENCY_PRODUCTION_LIMIT=5
  - N8N_GRACEFUL_SHUTDOWN_TIMEOUT=600000  # 10 minutes

  # === GESTION DES DONNÉES ===
  - N8N_DEFAULT_BINARY_DATA_MODE=filesystem
  - N8N_AVAILABLE_BINARY_DATA_MODES=filesystem,default
  - EXECUTIONS_DATA_MAX_AGE=72  # 3 jours
  - EXECUTIONS_DATA_PRUNE=true
  - EXECUTIONS_DATA_PRUNE_MAX_COUNT=1000

  # === FEATURES & SÉCURITÉ ===
  - N8N_RUNNERS_ENABLED=true
  - N8N_METRICS=true
  - N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
  - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true
  - N8N_BLOCK_ENV_ACCESS_IN_NODE=false
  - N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY}

  # === TIMEZONE ===
  - GENERIC_TIMEZONE=${TZ}

volumes:
  - n8n_data:/home/node/.n8n
  - ./local-files:/files

mem_limit: 6g
mem_reservation: 4g

networks:
  - main_network

depends_on:
  postgres:
    condition: service_healthy
5

Thank you @zlebandit
Can you confirm if the worker nodes are also running on 1.113.1 ?

6

Yes I confirm !

7

Can you set the following environment variable and test again, please?
N8N_ENABLED_MODULES=data-table

1 Like
8

@nikhilkuria it works with this environment variable added !

Sorry, I didn’t find it in the documentation page, so I prefered write here for the community :wink:

And with the first tests, it seems to go faster than a Postgres SLQ query for small quantity of data. Very nice !

2 Likes
9

No problem, this env variable is not really needed from v1.113.0. So, it’ll be great if you can double check if the runners are on the this version.
We’ll check if there is an edge case here.

Thanks a lot for reporting this and glad to see you like it :slight_smile: