n8n workflows that arrive configured, not blank.
77 importable workflows for the unglamorous parts of running a small business — onboarding a client, chasing an invoice, turning a booking into the six things that have to happen next. Import one and 71% of the nodes already have their fields written in.
The gap is never the wiring.
Anyone can draw four nodes on a canvas and connect them. The work is deciding what goes in them: what the reminder actually says, how long to wait before sending it, which columns the sheet needs, what the filter is really testing. That is the part a blank template leaves to you, and it is the part that takes the afternoon.
So it is the part that ships written. Across 77 workflows and 479 nodes, 342 arrive with their fields filled in — subject lines, message bodies, task names, delays, spreadsheet columns, filter thresholds — and each one is a decision already made rather than a blank waiting for you to make it.
What an import cannot carry.
Your credentials
No workflow file can carry these, by design, and you would not want one that did. You connect each account in n8n the normal way.
Ids only your account knows
Which spreadsheet, which Slack channel, which Trello board. These are internal ids, and writing a human-readable name into an id slot produces a workflow that imports cleanly and then does nothing. So those stay blank, named in a sticky note under the node.
That rule decides everything else too. A parameter is written in only when it was checked against the schema a real n8n publishes for that node — never because the field name looked similar. The build fails rather than shipping an invented parameter, because n8n stores an unknown key and ignores it: the node looks configured, and nobody ever opens a node that looks configured.
Where an app has no native n8n node at all, the step arrives as an empty HTTP Request node with the reason written beside it. That is on purpose. An empty HTTP Request node is visibly unfinished and you will go and finish it; a plausible-looking wrong node is not.
There is one exception, and it is stated rather than hidden. Google Forms has no n8n node, so in 13 of these workflows that step is a native Google Sheets node on the form’s linked responses sheet — the same data under the same field names, by the route an n8n user would take anyway. Those nodes are named for what they are, not for what they stand in for, and the first line of the sticky note under each one says which app it is replacing. You should never have to discover that by opening it.
Open one and check.
Coaching Session Cycle
Automate the prep, reminder, notes and follow-up around every coaching session.
8 nodes, every one native and every one configured · €19
Podcast Guest Pipeline
Move guests from booked to recorded to promoted without chasing anything by hand.
8 nodes, every one native and every one configured · €19
Appointment Reminder & No-Show Recovery
Cut no-shows with timed reminders and win back the ones who still miss.
7 nodes, every one native and every one configured · €14
Month-End Close Checklist
Run the same closing sequence every month, per client, without keeping it in your head.
7 nodes, every one native and every one configured · €24
Discovery Call Machine
Turn every booked call into a prepped, reminded and followed-up meeting automatically.
6 nodes, every one native and every one configured · €14
Subscription & Renewal Tracker
Get warned before every software renewal and contract auto-renews.
6 nodes, every one native and every one configured · €14
Thirty seconds, no typing.
Import the file
In n8n, the ⋯ menu top right → Import from File, and pick the .n8n.json.
Or just paste it
Open the file, select all, copy, click the empty canvas and press Ctrl+V. n8n recognises the JSON and draws the whole thing.
Or install a batch
Every download ships a small dependency-free installer script that pushes every workflow beside it through your own n8n API in one go. It has a --dry-run, it talks to no host but the one you name, and it never prints your key.
The workflow arrives switched off and with no accounts attached, which is the state you want to start from.
3 free ones, no account needed
Download the workflow, import it, and judge the rest of the library by it. No email required.
Coming from Zapier? The same recipes ship as Zapier build guides and Make guides in the same purchase — how each platform is delivered →