Block 1 - If
- Type / Role
- n8n-nodes-base.if - if
- Config choices
- Version 2.2
This workflow is provided as-is. Please review and test before using in production.
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, rece...
n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.webhook, n8n-nodes-base.respondtowebhook, n8n-nodes-base.code, n8n-nodes-base.ssh, n8n-nodes-base.switch, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by PUQcloud.
Original n8n.io sourceThe 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 Docker installed to perform predefined actions.
You have two options:
Create a Basic Auth Credential for the Webhook API Block in n8n.
Create an SSH Credential for accessing a server with Docker installed.
In the Parameters block of the template, update the following settings:
server_domain – Must match the domain of the WHMCS/WISECP Docker server.clients_dir – Directory where user data related to Docker and disks will be stored.mount_dir – Default mount point for the container disk (recommended not to change).Do not modify the following technical parameters:
screen_leftscreen_rightIn the Deploy-docker-compose element, you have the ability to modify the Docker Compose configuration, which will be generated in the following scenarios:
In the nginx element, you can modify the configuration parameters of the web interface proxy server.
Management of Docker containers and all related procedures on the server is carried out by executing Bash scripts generated in n8n. These scripts return either a JSON response or a string.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 34 workflow blocks. Download the JSON for the full node graph.
| Workflow | Deploy Docker n8n, API backend for WHMCS/WISECP |
|---|---|
| Complexity | advanced |
| Nodes | 34 |
| Categories | DevOps |
| Author | PUQcloud |
| Published | 17 Mar 2025 |
Use the JSON export at /data/workflows/3197/3197.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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, rece...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.