Deploy Docker n8n, API backend for WHMCS/WISECP
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 33 nodes and runs when an HTTP GET request hits its webhook URL. It uses only n8n's built-in nodes.
How it runs
Trigger: When an HTTP GET request hits its webhook URL.
- Parametrs (Edit Fields (Set)): sets 5 fields: server_domain, clients_dir, mount_dir…
- If: checks a condition and branches into true / false
- Container Stats (Switch): routes items into 3 branches
- Container Actions (Switch): routes items into 7 branches
- n8n (Switch): routes items into 3 branches
- If: checks a condition and branches into true / false
- 422-Invalid server domain (Respond to Webhook): sends the response back to the webhook caller
- Inspect (Edit Fields (Set)): sets 1 field: sh
- Stat (Edit Fields (Set)): sets 1 field: sh
- Log (Edit Fields (Set)): sets 1 field: sh
…plus 22 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook - Code
n8n-nodes-base.code - SSH
n8n-nodes-base.ssh - Switch
n8n-nodes-base.switch
From the author
Setting up n8n workflow Overview The Docker n8n WHMCS module uses a specially designed workflow for n8n to automate deployment processes. The workflow provides an API interface for the module, receives specific commands, and connects via SSH to a server with…