N8N on WebspaceKit — Unlimited Automations for $6/Month, Zero Terminal Required

ARTICLE BODY:

What this solves

n8n Cloud's Starter plan costs $20/month and caps your workflow executions. Build serious automations — daily triggers, webhook listeners, AI API calls — and you hit that cap within days.
Self-hosting removes the cap. But the usual path requires Docker setup, SSL configuration, reverse proxy management, and ongoing server administration. Most people look at that list and go back to the cloud plan.
WebspaceKit's managed n8n hosting is the third path: you get self-hosted pricing and unlimited executions, with zero server administration. The entire setup runs in under five minutes. No command line. No Docker.

Step 1 — Navigate to the n8n hosting page

Go to webspacekit.com/n8n-cloud-hosting/ and scroll down to the pricing section. Click "Choose Plan."
You will see billing period options: monthly, 12 months, and 24 months. The longer the commitment, the lower the monthly rate. For testing: 12 months. For production business automations you are already committed to: 24 months for the lowest per-month rate.

Step 2 — Create your account and complete payment

Fill in your name, email, and billing details. This is your WebspaceKit account — different from the n8n login you will create in Step 5.
Once payment completes, you are taken to your client area dashboard.

Step 3 — Find your n8n service

In the client area, your active services appear in a list. Click on your n8n hosting service. Look for the "Go to Setup" button and click it.
This opens the n8n initialisation page — a simple form with three fields.

Step 4 — Configure your n8n instance

Three fields:

`Owner First Name:  your first name
Owner Email:       your n8n login email
Owner Password:    strong password for your n8n dashboard`

Important: the Owner Email and Password here are your n8n login credentials — separate from your WebspaceKit account credentials. Use different passwords for each.
Click "Next" or "Complete Setup."

WebspaceKit provisions your instance. This takes 30–60 seconds. When the success screen appears, you will see your n8n dashboard URL:
https://your-instance.webspacekit.com
Click it. Your n8n instance opens.

Step 5 — First login and orientation

Log in with the email and password you set in Step 4.
Your dashboard loads with whatever starting template came with your plan. If you are on a plan that includes pre-built workflow templates, you will see those immediately in your workflows list.

The main panels:

`Workflows     — your automation canvas list
Credentials   — OAuth connections to your apps
Executions    — logs of every workflow run
Settings      — n8n configuration and user management`

Step 6 — Connect your first app

Every app n8n connects to requires a credential. For Gmail:

Settings → Credentials → New Credential → search "Google"
Select "Google OAuth2 API"
Follow the Google authorisation flow
Save the credential

That credential is now available to every Gmail node in every workflow you build. You authenticate once per service, not once per workflow.
Common credential types to set up immediately:

`Google (OAuth) — Gmail, Google Sheets, Google Drive
Notion (API key) — databases, pages
Slack (OAuth) — messages, channels
HTTP Request (no auth) — public APIs

`

Step 7 — Build your first workflow

Click "New Workflow" → drag a Schedule Trigger onto the canvas.
A minimal daily briefing workflow to start:


Node 1: Schedule Trigger
Mode: Days
Hour: 8
Minute: 0

Node 2: HTTP Request
Method: GET
URL: https://hacker-news.firebaseio.com/v0/topstories.json?limitToFirst=5&orderBy="$key"

Node 3: Gmail — Send Message
To: [e-mail]
Subject: Morning Briefing — {{ $now.toLocaleDateString() }}
Body: {{ JSON.stringify($json, null, 2) }}
plaintext

Wire them in sequence. Click "Execute Workflow" to test. Check your inbox.

That is the pattern. Every workflow in n8n follows the same structure: trigger → action(s) → optional logic nodes.
The workflows that actually save the most time

Three high-ROI starting points based on usage patterns:


Lead capture from form submissions → CRM:
Webhook Trigger → HTTP Request (validate data) →
Notion (create page in leads database) →
Gmail (send confirmation email)
Daily social content scheduler:
Schedule Trigger (9 AM) →
Google Sheets (read next queued post) →
HTTP Request (post to Twitter/X API) →
Google Sheets (mark row as posted)
Automatic invoice processing:
Gmail Trigger (attachment received) →
Extract attachments →
Google Drive (save to invoices folder) →
Notion (log invoice details)
Each of these replaces 15–30 minutes of daily manual work. At three workflows running daily, you recover roughly an hour per day within the first week.


What tends to break on first setup

Google OAuth redirect error: add your WebspaceKit n8n instance URL to the list of authorised redirect URIs in your Google Cloud Console OAuth app settings. Takes two minutes.

Workflow triggers but produces no visible output: check the Executions tab. Every execution is logged with full node-by-node data showing exactly what passed between nodes and where execution stopped.
Schedule Trigger not firing: confirm the workflow is Active (toggle in top right of the workflow editor, turns blue when active). A workflow in Test mode only fires when you manually trigger it from the editor.
Webhook URL not receiving data: WebspaceKit assigns you a fixed subdomain. Confirm the webhook URL in your n8n Form Trigger matches what you have registered in the external service.

Scaling up

Once the basic setup is running cleanly, the natural next steps:
Add error handling to critical workflows. An Error Trigger node catches any workflow failure and sends you a notification. For workflows that touch client data or financial systems, this is not optional.
Error Trigger → Gmail (send failure alert with error details)
Build a workflow template library. Export your best workflows as JSON (top menu → Download) and keep them in a folder. When you build for a new use case, start from the closest matching template rather than from scratch.

Connect n8n to your AI workflows. The HTTP Request node handles any API call — including OpenAI, Anthropic, or any LLM provider. This is how you build the kind of AI-powered automations covered elsewhere on this blog (news-to-WordPress, Instagram comment response, video generation pipelines) without needing a separate orchestration layer.

Full setup guide with every screenshot at elevoras.com.
Automating something interesting on WebspaceKit or running into a node configuration issue? Drop it in the comments.