xCloud × n8n: Running WordPress and Automation Workflows on the Same Server

Want to self-host n8n without dealing with Docker and server settings? This article demonstrates how to use One Click Apps on xCloud to quickly deploy n8n, sharing the same server with an existing WordPress site, complete with backups, SSL, and resource monitoring, creating a stable and easy-to-maintain automation workflow environment.

In "xCloud Review: From 0 to Next-Gen Cloud Host Control Panel", we introduced xCloud's basic interface, pricing model, and actual performance on WordPress.

This article focuses on another key capability: self-hosting n8n on xCloud to automate your existing WordPress ecosystem, and even operate alongside other services on the same server.

The article will be divided into several parts:

Understanding n8n and why it's suitable for deployment on xCloud
How to deploy n8n on xCloud and share the same host with WordPress
Basic maintenance and security settings
Advanced n8n application topics (separate tutorials will be added later)

If you already use WordPress for content, forms, or e-commerce and want a backend that "runs processes for you automatically," xCloud + n8n is an ideal next step.

What is n8n?

A self-hostable automation workflow platform

n8n is an open-source automation workflow tool that connects different services and APIs, allowing you to design automations using flowcharts. Features include:

Visual interface for designing flows, with nodes presented via connections
Built-in nodes for many common services (HTTP Request, Webhook, Databases, Slack / Telegram, etc.)
Supports JavaScript / TypeScript nodes for handling complex logic
Offers both self-hosted and cloud modes; the self-hosted version provides full control over data and environment

For users accustomed to managing their own servers, n8n can be seen as "a backend dedicated to automation processes," centralizing scripts that were previously scattered everywhere.

The threshold for traditionally self-hosting n8n

If you don't use xCloud and self-host n8n on a VPS manually, you usually have to handle:

Installing Node.js or using Docker directly
Setting up Nginx / Reverse Proxy and SSL certificates
Managing environment variables (API Keys, encryption keys, Webhook URLs, etc.)
Planning backup and version update processes
Adjusting n8n deployment settings and security options according to official documentation

These tasks aren't inherently difficult, but they are fragmented and require writing your own deployment/restoration SOP.

xCloud's One Click Apps aim to take care of this server and environment setup work, allowing users to spend more time actually designing workflows.

What can xCloud offer for n8n?

For n8n, xCloud acts as the "host and control panel":

One-click deployment of n8n using One Click Apps
Managing multiple sites on the same server (WordPress, n8n, Uptime Kuma...)
Handling domains, SSL, backups, and basic resource monitoring
Centralizing n8n environment variables in the dashboard management, eliminating the need to edit config files everywhere

For users who already host WordPress sites on xCloud, the learning curve for deploying n8n is relatively low.

Architecture and Host Planning: Running WordPress + n8n on the Same VPS

The concept of multiple Sites on one host

xCloud pricing is based on the "number of servers," and a single server can host multiple Sites. For users, the structure looks like this:

One VPS
Hosting one or more WordPress Sites on it
Simultaneously hosting an n8n Site, or even adding tools like Uptime Kuma

xCloud-wordpress-n8n-in-one-server — WordPress + n8n can be created on the same server

Each Site in xCloud has independent settings pages, Domain management, backups, and logs. They operate independently but share the resources of the same machine.

Practical Reference for CPU / RAM

n8n's resource requirements depend on the complexity of the workflows. General VPS specifications for n8n are:

Minimum: 1 vCPU, 2 GB RAM, and about 20 GB SSD to get it running
Recommended starting point: 2 vCPU, 4 GB RAM, providing more headroom for more flows and API calls

n8n doesn't use much memory when idle; what really consumes resources are tasks within workflows: e.g., heavy API fetching, file processing, or long-polling external services.

If the same host also needs to run 1–2 small-to-medium WordPress sites, consider these common combinations:

2 vCPU / 4 GB RAM:
- 1~2 small-to-medium WordPress sites
- 1 n8n setup, executing standard API calls and notification flows
4 vCPU / 8 GB RAM:
- Multiple sites or WordPress sites with e-commerce traffic
- n8n handling more reporting, synchronization, and scheduled tasks

If you already have a primary WordPress host on xCloud, assess current resource usage before deciding whether to upgrade RAM/CPU or spin up a second server dedicated to n8n.

Domain Planning: Main Site + Automation Subdomain

It is recommended to isolate n8n on a subdomain for easier identification and control:

WordPress Main Site: https://example.com
n8n Dashboard: https://n8n.example.com or https://automation.example.com

The benefits are:

The URL is easy for team members to remember
It's clear at a glance in the xCloud Site list
Adding Basic Auth or firewall rules to n8n later won't affect other websites

Implementation Process: Deploying n8n on xCloud

Step 1: Confirm Server Type

n8n runs as a Node.js application on xCloud. Since official documentation and tutorials mostly use Nginx, if you haven't chosen a Web Server yet, Nginx is the more versatile combination.

If your current WordPress is on an OpenLiteSpeed server but you want to follow the documentation for n8n, you can:

Keep the original OLS server running WordPress exclusively
Create a separate Nginx server dedicated to running n8n

Or simply choose Nginx as the shared Web Server from the start.

Step 2: Create n8n Site from One Click Apps

Log in to the xCloud Dashboard
Click "+ New Site" in the overview screen or target server
After selecting the server, switch to the One Click Apps tab
Select n8n from the list

xCloud-n8n-new-site1 — Click "+ New Site" in the overview screen or target server

xCloud-n8n-new-site2 — Click "+ New Site" in the overview screen or target server

Next, you will enter the n8n Site settings screen.

Step 3: Site Basic Information and Deployment Mode

You need to fill in the creation screen:

Site Title: Purely for your own identification, e.g., "n8n – automation"
Tags: You can enter tags like n8n, automation

Next, there are two modes to choose from:

Go Live: Create a production environment directly
Demo Site: Test using a temporary subdomain provided by xCloud first

Note that if a Demo Site is later converted to a production site, the original demo domain cannot be used anymore, so plan the final domain name before going live.

xCloud will automatically populate:

Default Port
Default Site User

Keeping the defaults is usually fine. More important than tweaking these values is:

Set the Time Zone to your local time zone, such as Asia/Taipei, so that n8n schedules and logs match your time

After confirming, submit it, and xCloud will start deploying n8n in the background.

Step 4: Configure Domain and SSL

After deployment is complete, enter the "Domain" tab of this n8n Site:

During the testing phase, you can test using the demo domain provided by xCloud
When ready to go live, add a production domain like n8n.example.com
Enable Let’s Encrypt or apply a custom certificate to enable SSL

The process here is very similar to setting up a WordPress Site, just pointing to a different Site.

Step 5: First Login to n8n

In the xCloud Dashboard, click "Visit Site" on the n8n Site, and the browser will open the n8n initial screen:

Enter the admin Email and password to complete registration.

Then you will see the n8n main screen and workflow editor.

Up to this point, n8n is successfully running on xCloud, and you can start building basic flows.

Step 6: Manage n8n Settings using Environment

xCloud centralizes application environment variables in the "Environment" interface. For n8n, common adjustments include:

Base URL and host-related settings to ensure Webhook URLs are correct
Time zone settings
Basic access protection (such as enabling n8n's Basic Auth mechanism)
Connection information for SMTP or external services

These settings might originally require modifying .env files or container parameters via SSH. Centralizing them in the xCloud backend makes them easier to maintain and less prone to omissions.

Step 7: Version Updates

When n8n releases a new version in the future, you can check version info and perform updates in the "Updates" section of this Site.

A more robust approach is:

Create a backup for the n8n Site first
Then perform the version update
If you encounter problems, you can restore the entire Site directly from the backup

Combined with xCloud's scheduled or incremental backups, this process can be replicated regularly, keeping n8n in a safe and recoverable state over the long term.

Integration with WordPress: How can you use n8n?

Treat this chapter as an "application map" listing several common scenarios to help visualize n8n's place in the overall architecture. Implementation details will be fully broken down in their respective n8n tutorials.

Forms and Customer Inquiries: From Submission to Trackable Process

Paired with common WordPress form plugins (e.g., Fluent Forms, SureForms, etc.), n8n can take over:

Receiving Webhooks when forms are submitted
Formatting field content and transcribing it to Slack / Discord / Email
Syncing to Google Sheets, CRM, or Notion

Making inquiries not just land in the inbox, but immediately enter a trackable automation flow, where you can decide later whether to segment, tag, or auto-reply.

E-commerce Events: Orders, Subscriptions, and Post-Sales Processes

For WooCommerce, FluentCart, or SureCart users, n8n can act as an "e-commerce event hub":

Triggering notifications and report entries when orders are completed or refunded
Helping organize lists when subscriptions renew or fail
Syncing key order data to Google Sheets, FluentCRM, or other internal systems

These processes can reduce manual order processing time and integrate important events into a single automation platform.

Reports and Scheduled Tasks: Unifying Schedules with n8n

n8n's schedule nodes can replace some WP-Cron jobs or custom scripts:

Generating revenue/content performance reports daily and sending them to the team
Periodically fetching data from external APIs and updating it to WordPress or spreadsheets
Managing status for members or subscriptions meeting specific conditions

These tasks inherently require scheduling and retry mechanisms; managing them centrally in n8n makes debugging and adjustment easier.

Operations and Security: Basic Principles for Managing n8n on xCloud

Extra Layer of Protection: Basic Auth + Firewall

Although n8n has its own login mechanism, in practice, it is recommended to add another layer in front:

Use n8n's N8N_BASIC_AUTH_* environment variables to enable Basic Auth
Use xCloud's firewall or Cloudflare rules to allow access only from specific IPs or countries

For workflows containing API Keys and OAuth credentials, this layer of protection is crucial.

Backup and Restore Strategy

n8n workflows, credentials, and execution logs are usually stored in a database. xCloud's backup mechanism can package the entire Site (code + database) together.

In practice, you can arrange it like this:

Enable scheduled backups (daily or weekly)
Create a manual backup before making major workflow changes or updating n8n
When moving hosts is necessary, use xCloud's restore function to restore the n8n Site to a new server

Monitoring Resources and Adjusting Specifications

As the number of workflows increases, you can observe via xCloud's monitoring and Log functions:

Whether CPU and RAM usage consistently spike during peak hours
Whether n8n frequently encounters 5xx errors or connection timeouts

If n8n starts hosting more reports, synchronization, and scheduled tasks, consider:

Upgrading existing host specifications
Moving n8n to a dedicated server

Conclusion

For readers already using xCloud to run WordPress, n8n is a natural extension:

No need to get used to a new control panel
You can run a content site and an automation backend on the same host simultaneously
Through One Click Apps, save the tedious steps of installing n8n yourself

If you are not familiar with xCloud itself, you can look back at "xCloud Review: From 0 to Next-Gen Cloud Host Control Panel" to understand the overall architecture and pricing before planning whether to add an n8n backend on it.

If you are interested later, you can further integrate tools like Cloudflare and Uptime Kuma to create your own "automated operations dashboard," making daily maintenance of WordPress and various services easier.