15351 workflows · 7615 call a model · 61 services · 5286 small enough to read in one sitting

Automations, described by what they do

Every one of these arrived with a paragraph written to sell it. We threw those away. What you read here is composed from the workflow's own steps: what starts it, which services it touches, whether it hands judgement to a model, and how many pieces there are to understand.

That means the descriptions are checkable, and that some of them are unflattering. A workflow that turns out to be four steps and a webhook is described as four steps and a webhook. You can decide from the page whether it is worth your afternoon, which is the only thing a library like this is for.

What they're for

What we took out

These files carry more of whoever built them than is obvious: the identifier of the n8n instance they were exported from, canvas notes holding personal links and email addresses, saved credential names, and in places a real spreadsheet belonging to a real person. All of it is stripped before anything is stored. Every file was checked, not sampled.

What remains is the mechanism: the steps, their settings and how they connect. Where an author had left a live document behind, it is replaced with the same placeholder the careful ones used, so you can still see what belongs there.