javierroques
← All notes
Automationn8nSoftware

5 n8n Workflows I Actually Use Every Day

Real automation workflows I've built with n8n — not toy examples, but things that run daily and save me from doing things manually.

·3 min read

I've been self-hosting n8n for about a year now. In that time I've built probably 40 workflows, deleted half of them when they turned out to be useless, and refined the rest. Here are the five that have survived and that I actually rely on.

1. Morning Briefing

Every weekday at 7:30 AM, a Telegram message lands with:

  • Today's calendar events (Google Calendar API)
  • Weather for the day (Open-Meteo, free, no key)
  • Any GitHub PRs awaiting my review
  • Home Assistant energy summary from yesterday

The message is formatted with Markdown and emoji because I'm not a monster.

// Sample output
{
  "text": "☀️ *Good morning!*\n\n📅 *Today:* 2 meetings\n🌤 23°C, partly cloudy\n🔴 2 PRs need review\n⚡ Yesterday: 8.4 kWh used, 3.1 kWh solar"
}

The n8n workflow has about 12 nodes. The key is a Merge node that waits for all parallel data fetches to complete before the message is assembled.

2. Package Tracking

Every morning, n8n scrapes my Gmail for shipping confirmation emails (label: shipping), extracts tracking numbers using regex, queries the carrier API (17TRACK supports 1,400+ carriers), and sends me a summary of packages in transit.

This sounds trivial but it's replaced an app I was paying $4/month for.

3. Home Assistant Alert Routing

Covered in detail in my notification router project, but the short version: HA sends all alerts to an n8n webhook, which applies priority, silencing, and deduplication rules before routing to Telegram or Pushover.

Without this, HA was sending me 50+ notifications a day, most of which I didn't care about at that moment.

4. Link Saver → Obsidian

When I forward a URL to a specific Telegram chat, n8n:

  1. Receives the message via Telegram trigger
  2. Fetches the page metadata (title, description, OG image) via HTTP Request
  3. Generates a Markdown note with frontmatter
  4. Saves it to my Obsidian vault via the Obsidian REST API plugin
# Generated note format
---
title: "The Article Title"
url: https://example.com/article
saved: 2025-01-22
tags: [inbox]
---
 
> The article description here.
 
[Open article](https://example.com/article)

Beats manually copying links into Obsidian by a mile.

5. Server Health Digest

Every Sunday at 9 AM, n8n polls my self-hosted services and sends a health digest:

  • Uptime Kuma status for all monitors
  • Disk usage on each machine (via Netdata API)
  • Any Docker containers that have been restarting
  • SSL certificate expiry dates (alerts if < 30 days)

It's a weekly forcing function to notice issues before they become outages.

Tips for Building n8n Workflows

Use webhook triggers liberally. Every service that can send a webhook should. Polling is fine for some things, but webhooks give you instant reaction.

Error workflows are underrated. Set up a single error workflow that catches failures and sends them to Telegram. You'll actually know when things break.

Keep workflows focused. I tried building one giant "everything" workflow and it became unmaintainable. One workflow per logical function is much easier to debug.

Pin test data. During development, use n8n's "pin data" feature to freeze node outputs so you can iterate on downstream nodes without re-triggering the whole chain.

n8n is one of those tools that keeps paying dividends. Every hour I spend setting up a workflow pays back hours over the following months. If you're not already self-hosting it, the Docker setup takes about 15 minutes.

← Back to all notes