n8n workflows that run in production

n8n is a program for wiring company systems together without writing everything from scratch: it pulls data from one place, reshapes it and puts it into another. That sounds simple right up to the first API rate limit, the field that sometimes arrives empty, or the public register that goes quiet for an hour once a week. That is where the gap shows between a demo and something a company runs every day — the gap is not a few more blocks, it is handling every case where something fails.

This section is about that gap. There are no “connect node A to node B” tutorials here; the internet has a thousand of those. What is here is the part usually missing: which exact case breaks the flow, what the API returns when the data is incomplete, how the error path behaves, and how much work the workflow really takes off a person. Every write-up is produced after the rollout, not before it.

Each document shows who wrote it, who reviewed it and when — together with the n8n version it was tested on. That matters, because n8n moves fast and a year-old description may no longer match the interface. When something stops being true, the page gets a new verification date and a changelog entry instead of quietly going stale.

We publish the workflow files in the form we use them: JSON to import, a GitHub repo, sometimes a template on n8n.io. Take them and run them yourself. If you would rather have someone assemble it and keep it running, that is what we do — but nothing here is gated.