Phase 19

n8n

Prerequisite: Immich

n8n is a workflow automation platform.

It is useful when you want to glue services together without writing an entire custom application every time. Think schedules, webhooks, API calls, notifications and data transformations.

It is one of those tools that can either be extremely useful or become a procrastination machine, so deploy it with a purpose.


Good Uses for n8n in a Home Server

Examples that make sense:

  • send yourself alerts when something fails
  • move or transform files automatically
  • call APIs on a schedule
  • glue together self-hosted tools that do not integrate cleanly on their own

Examples that usually do not make sense:

  • rebuilding a simple shell script as a giant drag-and-drop diagram because a GUI feels fancy

Keep the bar high.


Create the Directories

mkdir -p ~/docker/appdata/n8n
mkdir -p ~/docker/compose/automation

Create the Compose File

Create ~/docker/compose/automation/n8n.compose.yml:

services:
  n8n:
    image: n8nio/n8n:latest
    container_name: n8n
    ports:
      - "5678:5678"
    environment:
      - TZ=America/New_York
      - NODE_ENV=production
    volumes:
      - /home/<your-user>/docker/appdata/n8n:/home/node/.n8n
    restart: unless-stopped
    networks: [proxy]

networks:
  proxy:
    external: true

Start it:

docker compose -f ~/docker/compose/automation/n8n.compose.yml up -d

Then open:

http://<nixos-ip>:5678

Security Note

n8n can end up holding:

  • API keys
  • webhook endpoints
  • credentials for other services

So treat it like an admin tool, not a casual public dashboard.

My recommendation is to keep it:

  • LAN only
  • or Tailscale only

unless you have a very specific reason to expose it and know how you are going to secure it.


Start Small

Your first workflows should be boring and useful.

For example:

  • send a message when a backup completes
  • hit a health endpoint on a schedule
  • copy attachments from one place to another

Do not start by building a giant Rube Goldberg machine that depends on ten services and breaks in five different ways.


Next Steps

Next, we will cover local LLMs, which is where the hardware choices from earlier can start to matter much more.

Proceed to Local LLMs.


Last updated: March 2026