The Execute Command docs say it is disabled by default from n8n 2.0. I’m running self-hosted n8n 2.32.7 on OpenShift. The workflow shows Unrecognized node type: n8n-nodes-base.executeCommand. There is no NODES_EXCLUDE in the Deployment. What is the supported way to enable this node in n8n 2.x? Is there a specific environment variable or configuration setting?
Hi @hemchandra, n8n 2.x excludes Execute Command by default, including when NODES_EXCLUDE isn’t set in your Deployment.
The documented way to enable blocked nodes is to set NODES_EXCLUDE to [] in the Deployment and restart the pods:
- name: NODES_EXCLUDE
value: '[]'
This clears the whole exclusion list, including other nodes excluded by default. If you want to keep any nodes blocked, list those node types instead, leaving n8n-nodes-base.executeCommand out. In queue mode, apply the setting to the workers too.
Execute Command runs shell commands inside the container executing the workflow, with that container’s permissions. Please make sure that access is appropriate for your workflow authors and deployment.