n8n-automation in Practice: Escaping Zapier

A complete self-hosted workflow automation guide

---

My first serious encounter with n8n came after being pushed to the breaking point by Zapier.

I had a simple requirement: monitor an RSS feed, push new content to a Telegram group, and archive titles and links to a Google Sheet. Zapier could do it, but the free tier was capped and an upgrade would cost $20/month. Not that I couldn't afford it — it just wasn't worth that price for something so simple.

Then I found n8n. Self-hosted, open source, free. Pull the Docker image, half an hour to set up, Zapier's annual fee saved.

What Is n8n? One-Sentence Version

A workflow automation platform. Visual drag-and-drop to connect services — trigger an event → execute a chain of actions. Same category as Zapier and Make (formerly Integromat), but fully self-hostable, with full JavaScript code nodes, complex branching logic, and developer-friendliness.

In OpenClaw, we use the n8n-automation skill to manage n8n workflows — right from a conversation, without opening the browser UI.

Getting n8n Running

The simplest way is Docker:

docker run -it --rm \
  --name n8n \
  -p 5678:5678 \
  -v ~/.n8n:/home/node/.n8n \
  docker.n8n.io/n8nio/n8n

Access http://localhost:5678, register an account, and you're in.

For long-term server deployment, Docker Compose is more stable:

version: '3.8'
services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "5678:5678"
    volumes:
      - ~/.n8n:/home/node/.n8n
    environment:
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=your_password
      - WEBHOOK_URL=https://your-domain.com/

WEBHOOK_URL is important — set it to your public address if you want external services (GitHub webhooks, Telegram bots) to reach n8n.

Configuring the n8n-automation Skill

Find and install the n8n-automation skill in OpenClaw. It needs two config items:

• n8n URL: Your n8n instance, e.g., http://localhost:5678 or https://n8n.yourdomain.com
• API Key: Generate from n8n UI at Settings → API → Create API Key

Once configured, you can operate n8n with natural language in OpenClaw: "List all workflows" and the skill calls the n8n API automatically.

First Real Workflow: AI Content Monitoring

A workflow we actively use: monitoring AI-related keywords on Twitter/X, using GPT to filter, and pushing quality content to our Telegram channel.

Flow design:

1. Schedule Trigger — runs hourly
2. HTTP Request — calls Twitter/X API to search keywords ("AI agent" OR "LLM" OR "Claude")
3. Code node — deduplicate, filter out posts with less than 50 retweets
4. OpenAI node — let GPT score content value (1-10), filter below 7
5. Telegram node — format and push to internal channel
6. Google Sheets node — archive

Through OpenClaw's n8n-automation skill, you can say: "Create a workflow that searches Twitter for AI keywords hourly, filters quality content with GPT, and sends to Telegram" — the skill generates the workflow JSON which you import directly into n8n.

The Code Node: n8n's Superpower

The biggest difference from pure drag-and-drop tools: n8n has a Code node that runs arbitrary JavaScript (or Python). Example:

// Code node: parse complex data structure
const items = $input.all();
const results = [];
for (const item of items) {
  const rawData = item.json.data;
  const flattened = rawData.entries.map(entry => ({
    id: entry.id,
    title: entry.content?.title || 'Untitled',
    timestamp: new Date(entry.created_at * 1000).toISOString(),
    score: entry.metrics?.engagement_score ?? 0
  }));
  const filtered = flattened.filter(e => e.score > 5);
  results.push(...filtered.map(f => ({ json: f })));
}
return results;

Error Handling: Don't Let Workflows Fail Silently

1. Set up an error workflow: In n8n settings, configure a global error workflow. Mine sends a Telegram message telling me which workflow failed and why.

2. Add try/catch at critical nodes: HTTP Request nodes have "On Error: Continue" — enabling it prevents the whole flow from stopping on a single node failure.

3. Regularly check execution history: I use OpenClaw weekly: "Check if n8n had any failed executions this week" — the skill pulls the execution log and filters failures.

Triggering Workflows via OpenClaw Conversation

Common use cases without opening a browser:

• "Trigger the content scraping workflow" → skill calls n8n API directly
• "Check if any workflows failed today" → skill queries execution log and summarizes
• "Pause the daily report workflow, I'm traveling for three days" → skill disables the workflow
• "Change this workflow's trigger to 8am every day" → skill updates the Schedule node config

Pitfalls We Actually Hit

Webhook URL wrong: If n8n is on a local network, external webhooks can't reach it. Either set up a public address with reverse proxy, or switch to polling mode.

No alerts for expired credentials: OAuth tokens for Google Sheets, Gmail, etc. expire silently. Handle "401 Unauthorized" in your error workflow.

Large data volumes are slow: Use SplitInBatches node — process 100 items at a time for much better performance.

n8n has a gentle learning curve. The real value is knowing which repetitive tasks can be automated. The tool is just the tool — the thinking is the moat.