Unable to re-enable Execute Command node in n8n 2.0 using documented environment variables

Questions
1

After upgrading to n8n 2.0, the Execute Command node is disabled by default as per the breaking changes documentation.

I’ve attempted to re-enable the node using the N8N_NODES_INCLUDE environment variable as suggested, but the node still does not appear in the node selector.

Environment:

  • n8n version: 2.0

  • Installation method: System install (npm global) with systemd service

  • OS: Linux (Debian-based)

Steps to reproduce:

  1. Fresh n8n 2.0 install or upgrade from 1.x

  2. Add N8N_NODES_INCLUDE=n8n-nodes-base.executeCommand to environment file (/opt/n8n.env)

  3. Restart n8n via sudo systemctl restart n8n

  4. Search for “Execute Command” in node panel — node does not appear

1 Like
2

This is expected in n8n 2.0. The Execute Command node is disabled by default for security reasons.

If it’s still not showing, it usually means the setting isn’t being applied to the running instance or the service wasn’t fully restarted after the change.

Please double-check where n8n is hosted and ensure the instance restarted correctly.

:backhand_index_pointing_right: If you want, tell me how you’re running n8n and I’ll help you fix it quickly.

3

I am running n8n in systemd on Debian LXC

4

please see reply, ty

5

I found solution:

Add: NODES_EXCLUDE="[]"
To: opt/n8n.env

github feedback:
Note that the exact environment variable required is as follows: NODES_EXCLUDE="[]". After adding this variable, you should be able to see the nodes that were disabled by default in the nodes panel.

2 Likes