Automating the busywork with n8n

Most client work hides hours of repetitive glue: pull this feed, reformat it, notify that channel. n8n lets me wire those steps once and stop touching them — content pipelines, scraping, and the boring API plumbing in between.

What actually keeps automations alive

1. Model every node as a small idempotent step. If a workflow dies mid-run, I want to re-trigger it without double-posting or double-charging. Tiny, re-runnable steps make recovery trivial.
2. Push secrets to credentials, never inline. Tokens belong in n8n's credential store, not hardcoded in a node. It keeps exports shareable and rotation painless.
3. Add explicit error branches and retries. A silent failed automation is worse than no automation — you trust it, then it stops, and nobody notices. Wire the failure path to a notification.
4. Keep a human-in-the-loop checkpoint. Anything that sends a message or moves money gets a manual approval gate. Speed isn't worth an autonomous mistake.

On hosting: self-hosting buys control and cheaper scale; the cloud version buys uptime you don't babysit. I pick per project, not by reflex.