Why does my PowerShell script hang when executed via n8n's Execute Command node on Windows?

Below is some guidance on both parts of your question:

---

1. Community Nodes on the Desktop Version

Community nodes were originally built for self‑hosted environments, and there was a time when the Desktop App did not support them. More recently, the Desktop App has been updated so that custom (or community) nodes can be used if they’re placed in the proper custom‑nodes folder. In short, community nodes can now work with the Desktop App—but you must install them according to the custom node instructions. If you run into issues, double‑check that:

• You’ve installed the node into the correct folder (for Windows this is typically a folder like %USERPROFILE%\.n8n\custom\).

• You’ve restarted n8n so it picks up the new node.

---

2. Executing a PowerShell Script via n8n’s Execute Command Node

Since your PowerShell script runs fine when launched from a desktop shortcut, the fact that it runs but never “finishes” when triggered via the Execute Command node usually means the shell process isn’t exiting in a way that n8n can detect. Here are some pointers:

• Use the –File Option:
  Instead of directly embedding the script inline with -Command, try putting your script in a file and invoke it with the -File parameter. This tends to be more reliable than using inline commands. For example:

  BASHCopied
  powershell.exe -ExecutionPolicy Bypass -NoProfile -File "C:\path\to\your\script.ps1"

• Make Sure There’s No -NoExit:
  Check that you’re not inadvertently invoking PowerShell with the -NoExit flag (or any parameter that might keep the shell open).

• Confirm the Script Really Exits:
  Although you have an EXIT command in your script, verify that no other parts of the script (or any output buffering issues) keep the command process hanging. Sometimes verbose output can cause buffering issues—in such cases you may want to limit or redirect output if not required.

• Test with a Minimal Example:
  Try a bare‑bones script that does little more than output a line and exit, for example:

  POWERSHELLCopied
  Write-Host "Hello, world!"
  EXIT

  Then invoke it with:

  BASHCopied
  powershell.exe -ExecutionPolicy Bypass -NoProfile -File "C:\path\to\minimal.ps1"

  If this exits cleanly, then the problem may lie in how your more complex script handles output or completion.

---

In Summary

1. Community nodes: They now work with the Desktop App if installed in the proper custom nodes folder and loaded on startup.
2. PowerShell execution: Rather than passing the same parameters you use in your shortcut, try invoking your script with the -File parameter (making sure no parameters like -NoExit are present) so that the process naturally terminates. This approach is a common pattern for running PowerShell scripts via n8n's Execute Command node.

Give these suggestions a try, and if the issue persists, capturing any logs from n8n or further examining the process output might help identify if there’s buffering or a lingering process causing the hang.

Below is some guidance for your two questions:

---

1. Do community nodes now work on desktop versions?

Yes, community nodes are now supported in the desktop version of n8n—as long as they are installed correctly. Although older comments stated otherwise, recent versions (like your v1.77.3) are built on the same framework as self-hosted setups. You’ll need to follow the installation instructions for community nodes, and after restarting n8n Desktop you should be able to use them.

---

2. How to successfully execute a PowerShell script from n8n?

Since your script runs fine when launched from a desktop shortcut but then leaves the Execute Command node hanging, a few things should be considered:

• Exit Behavior:
  Confirm that your PowerShell script really ends all its processes. Instead of just having an EXIT (or exit) statement, try explicitly returning an exit code (for example, exit 0). This helps ensure that the process shuts down without waiting for unflushed outputs or orphaned child processes.

• Shell Invocation:
  Sometimes, invoking PowerShell through the command shell can resolve the hanging behavior. Instead of calling PowerShell directly, try wrapping it with cmd /c so that once the command completes, the command shell itself terminates. For example:

  BASHCopied
  cmd /c powershell.exe -ExecutionPolicy Bypass -NoProfile -File "C:\Path\to\script.ps1"

  This forces the execution to run as a subprocess that exits cleanly once done.

• Output Buffer Issues:
  Although your log file is being produced, check if the script produces any output that might exceed default buffer sizes. Even if it doesn’t, forcing the output to be redirected or minimized might help. For instance, if your script writes a lot of verbose or debug information to stdout, you might want to redirect or suppress those in your execution call.

• Using the Community Node:
  Given that a dedicated PowerShell community node exists (like the one you found on GitHub), installing and trying that might save you the headache. The community node is designed for executing PowerShell commands within an n8n workflow and might handle some of the quirks inherent to Windows command line environments better.

---

In summary:

• Community nodes now work in n8n Desktop, so you can consider using the PowerShell community node.
• For the Execute Command node, try invoking the script from cmd /c and ensure your PowerShell script ends with a clear exit code (e.g., exit 0).
• Also review if any output from your script might be causing the process to hang; redirecting or limiting output may help.

This setup should help your workflow exit the executing phase once the PowerShell script completes its run.