Can't enable execute command node

Questions
1

Describe the problem/error/question

I pulled the latest docker image of n8n to test some stuff on my pc.
One thing required me to move a file, which I wanted to do with the Execute Command node.
Can’t create a node of this type though.
I already set some environment variables to the compose.yml and made sure to recreate the container, but the node still doesn’t show up.

  • N8N_ENABLE_EXECUTE_COMMAND=true
  • N8N_BLOCK_ENV_VARS_IN_EXECUTE_COMMAND=false

What is the error message (if any)?

No error, just can't find the node.

Information on your n8n setup

  • n8n version: 2.8.3
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): -
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker Desktop
  • Operating system: Windows 11
2

Hello @prm

Since n8n v2.0, the Execute Command node is disabled by default via the NODES_EXCLUDE environment variable and must be explicitly re‑enabled. [v2.0 breaking changes; Block nodes]

To make the node appear again:

  1. Set NODES_EXCLUDE so Execute Command is not excluded

    Either enable all nodes:

    environment:
  - NODES_EXCLUDE="[]"

    or, if you only want to keep LocalFileTrigger disabled:

    environment:
  - NODES_EXCLUDE="[n8n-nodes-base.localFileTrigger]"

  2. Recreate the container

    After changing docker-compose.yml:

    docker compose down
docker compose up -d
3 Likes
3

The env var you want is NODES_INCLUDE or more likely you need to check that you’re setting the env vars in the right place in your compose file. They need to be under the environment: key for the n8n service, not at the top level. Can you paste the relevant part of your docker-compose.yml? Also double check the container actually restarted with docker compose down && docker compose up -d, sometimes docker compose restart doesn’t pick up env changes.

4

Welcome to the community @prm

Make sure your docker-compose.yml or compose.yml has the environment variables formatted correctly

services:
  n8n:
    image: n8nio/n8n:latest
    environment:
      - N8N_ENABLE_EXECUTE_COMMAND=true
      - N8N_BLOCK_ENV_VARS_IN_EXECUTE_COMMAND=false
    # ... rest of your config

After recreating the container, check if the environment variables are actually set:

docker exec <container-name> env | grep N8N_ENABLE

You should see:

N8N_ENABLE_EXECUTE_COMMAND=true
N8N_BLOCK_ENV_VARS_IN_EXECUTE_COMMAND=false

Sometimes a simple restart isn’t enough. Try:

docker-compose down
docker-compose up -d

Or if using newer Docker Compose:

docker compose down
docker compose up -d

After restarting the container:

  • Hard refresh your browser (Ctrl+Shift+R or Cmd+Shift+R)

  • Or open n8n in an incognito/private window

  • The node list is sometimes cached

docker exec <container-name> n8n --version

Let me know if the node still doesn’t appear after trying these steps.

1 Like
5

Hi, I needed to modify the NODES_EXCLUDE environment variable, the others didn’t work.

But your info about recomposing and making sure the list ain’t cached is very riveting.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.