I can't find the executive command on my server

I am not new to n8n but i just started using repocloud as a server to host n8n 1st time. I need execute command node but i tried many things like watching YouTube videos but still I have the same issue . Could you pls help?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

@Liruan The issue is likely because the Execute Command node is disabled by default for security. Since you’re on RepoCloud, you need to go to your dashboard, navigate to the Environment Variables section, and add N8N_BLOCK_SVC_COMMAND_NODE=false. After adding it, restart your instance and the node should work. Just keep in mind that it only executes commands available inside the n8n Docker container, so standard bash commands like curl will work, but you won’t have access to the host server’s root files by default.

@Liruan Execute Command is blocked by default on n8n 2.x for security reasons. on RepoCloud you fix it by setting an environment variable through their app dashboard.

open your n8n app in the RepoCloud panel, find the Environment Variables section (usually under Settings or Config), and add NODES_EXCLUDE with the value [] (literal empty JSON array — open square bracket, close square bracket). save and restart the app. after a hard browser refresh, search for “Execute Command” in the node panel, it should appear.

heads up: there’s an open issue (Unable to re-enable Execute Command node in n8n 2.0 · Issue #23439 · n8n-io/n8n · GitHub) where this sometimes doesn’t take effect on 2.x even when configured right — if Execute Command still doesn’t show up after the restart, that’s the bug, not RepoCloud.