Execute Command Node has removed

Feedback
1

Hi team,
I recently updated to n8n version 2.0.0, and I noticed that the Execute Command node is no longer available. This node is extremely important for many of my workflows, especially for tasks like:

  • Running server-side scripts

  • Handling FFmpeg commands

  • Executing custom shell operations

  • Automating local processing that can’t be done with built-in nodes

Right now, the absence of this node is blocking several of my automations.

Can you please bring back the Execute Command node or provide an official alternative/add-on for n8n v2.0.0?
This feature was heavily used and really essential for advanced workflows.

Thank you! :folded_hands:

Capture
Capture474×647 14.6 KB

3 Likes
2

usmanrehmani, i issued the same problem, but found this into releasing notes… this works for me

Disable ExecuteCommand and LocalFileTrigger nodes by default#

n8n will disable the ExecuteCommand and LocalFileTrigger nodes by default because they pose security risks. These nodes allow users to run arbitrary commands and access the file system.

Migration path: If you need to use these nodes, remove them from the disabled nodes list in your n8n configuration by updating the NODES_EXCLUDE environment variable. For example, set NODES_EXCLUDE="[]" to enable all nodes, or remove only the specific nodes you need.

3 Likes
3

Hi @Ian_Alves Thanks for the details however can you please guide where to add these in docker based installation. As suddenly my command node is not available and I have heavily used in my workflow.

4

Able to solve thanks :slight_smile:

5

Easiest way is to add the line to your .env and link to it via your .yml using docker compose. This as well as the folder block breaks several of my workflows as well. Would be nice if there was an easier “Babysitter Mode: On/Off” in settings, but I suppose if you know enough to change these settings, or know enough to get Claude or Codex CLI to do it for you, you are jumping over enough of a hill to prove you know the risk you are taking. Check for any remaining issues via 5678/settings/migration-report

6

FIX: If the Execute Command node is not visible in n8n, even after enabling it, this is likely due to recent changes in newer versions.

By default, the node is both disabled and excluded from the UI.

Here’s what worked for me on a self-hosted Docker setup:

  1. Open your docker-compose file:
    cd /docker/n8n
    nano docker-compose.yml

  2. In the n8n service, under environment:, add:

  • N8N_ENABLE_EXECUTE_COMMAND=true

  • NODES_EXCLUDE=[]

  1. Restart the containers:

docker compose down
docker compose up -d

  1. Refresh the n8n UI (hard refresh or open in incognito)

After this, the Execute Command node appears with the description:
“Runs a command on the host machine”

If you already had N8N_ENABLE_EXECUTE_COMMAND=true and the node still didn’t show, adding NODES_EXCLUDE=[] is what resolves it.

Tested on a VPS setup using Docker and Traefik.

3 Likes
7

Worked well, thank you!

1 Like