Five n8n Workflow Templates, Free to Download
Five workflows we run ourselves, as JSON you can import. Lead qualification, supplier bills into Xero, quote chasing, expiry warnings and client onboarding. No email, no signup.
Five n8n workflows we run ourselves, free to download and import. No email. No signup. No drip sequence waiting on the other side of a button.
Most template libraries are full of workflows that demo well and break on contact with a real business. They have one happy path, no error handling, and a prompt doing work that should have been arithmetic. These five are built the other way round. Boring where it counts.
Each one downloads as a JSON file. Import it and open the Configuration node. After that it’s a matter of connecting your own credentials.
1. Qualify and route inbound leads
Qualifying inbound leads is the job everyone automates first, and most get it wrong the same way. The usual build hands the whole thing to a prompt (read this enquiry, score it out of a hundred). Then the same enquiry scores 71 on Monday and 64 on Thursday, and nobody can say why.
This one splits the work. The model reads the enquiry and returns seven structured facts, and a Code node does the arithmetic. The same enquiry gets the same tier every time, with the reasons written onto the record.
The field normaliser (the step that maps whatever your form calls a field onto one standard name) handles about thirty-five different names for the same seven fields. Pointing it at someone else's form doesn't break it, which matters, because that's the most common reason an imported template dies on first run.
12 nodes. Form or Webhook, any AI model, HubSpot, Slack, Gmail.
2. Read supplier bills into Xero, ABN and GST checked
Bills arrive as PDFs and someone types them into Xero. A model can read them, and that’s where most builds stop. It’s also exactly how bad data gets in.
This one checks the numbers before anything is written anywhere. It runs a real ABN checksum, the modulus 89 algorithm the ATO publishes, so a transposed digit fails instead of being trusted because the model sounded confident. Then it cross-checks GST at ten per cent, confirms the subtotal and GST add up to the total, and throws out dates that aren't dates.
Bills that pass become drafts in Xero. Bills that fail go to Slack naming the check that failed. Nothing on a maybe.
11 nodes. Gmail, any AI model, Xero, Slack.
3. Chase unanswered quotes until someone replies
Quotes go out and then sit there. This one reads a register every morning, works out which quotes have gone quiet, and sends a follow-up worded differently each time. Three identical emails read like a robot. Three that acknowledge the time passing read like a person.
It stops the moment someone replies. Change the status in the sheet and that quote is never chased again.
9 nodes. Google Sheets, Gmail, Slack.
4. Warn before a licence or insurance lapses
Licences, insurances, white cards, trade tickets, first aid certificates. Every one has a date on it, and none of them announce themselves. This warns at sixty days, thirty days and seven, then daily once something has lapsed.
The part worth stealing is the suppression. Each item records which band it was last warned about, so sixty days sends once rather than every morning for a month. A warning nobody reads is worse than no warning, because it feels like cover.
9 nodes. Google Sheets, Gmail, Slack.
5. Run new client onboarding from one form
A client signs and five things need doing: a folder, a kickoff booking, a welcome email, a row in the tracker and a message to the team. Usually one person does all five, usually late, usually missing one.
Every name is worked out in a single node, so the folder naming can't drift. Two people naming folders by hand will produce Acme Pty Ltd and acme-pty-ltd-2026 in the same Drive inside six months, and sorting that out later means touching every link that ever pointed at either of them. That one is expensive to undo.
8 nodes. Google Drive, Google Calendar, Gmail, Google Sheets, Slack.
How to install them
It's the same five steps whichever workflow you picked. The first run takes about ten minutes, and most of that is connecting credentials.
-
Download the workflow you want
Pick a workflow above and download its JSON file. Nothing is gated, so no email is required.
-
Import it into n8n
In n8n, open the workflows list, use Import from File, and choose the JSON you downloaded. The whole workflow appears on the canvas with its documentation attached as sticky notes.
-
Connect your own credentials
Every node that talks to an outside service shows a credential warning. Open each one and pick your own connection. None of our credentials ship inside the files.
-
Edit the Configuration node
Each workflow has a single Set node named Configuration holding the things you are meant to change: thresholds, channels, schedules, wording. Everything downstream reads from it.
-
Run it once by hand before switching it on
Use Execute workflow and watch what each node returns on real data. Confirm the branches behave before you activate anything on a schedule or a live webhook.
Some of these won't suit you
If you send four quotes a month, the chaser solves a problem you don't have, and a calendar reminder does the same job for nothing. The bill reader earns its keep somewhere north of thirty invoices a month. Under that, typing them is faster than explaining the exceptions. We'd rather give a straight answer than have you import five workflows and run two.
These are starting templates for n8n workflow builds. Its cloud plans count executions, while self-hosting needs infrastructure and upkeep. AI calls add usage costs either way. Check n8n's current pricing against the volume you expect. We compare the billing units in n8n versus Zapier and n8n versus Make.
Before connecting live contacts, read the inbound lead-routing walkthrough. It covers the ownership, duplicate-event checks and failure handling the first template needs for a production setup.
When it doesn't work
n8n template FAQs
Yes, and there’s nothing to sign up for. The files are plain JSON on this page, with no email gate and no trial. We build automation for a living, so a workflow you can run yourself is an honest sample of how we work, not a lead magnet with the useful parts taken out.
No, though it helps for the Code nodes. Every workflow is designed so the only node you need to edit is Configuration, which is a plain list of values. The JavaScript inside the Code nodes is commented line by line if you want to change the logic, and safe to leave alone if you don’t.
Both. Every node used is a standard n8n node with no community packages, so nothing here depends on a self-hosted instance. Self-hosting only matters if your data can’t sit on someone else’s cloud, and that’s a compliance question, not a technical one.
The downloads are free. Running costs depend on your n8n plan or self-hosting setup, the connected tools and any AI calls. n8n Cloud counts workflow executions rather than each step, so volume can affect the plan you need. Check those costs before enabling real jobs.
Yes to both, including inside client work. They’re meant to be pulled apart. If one gets you most of the way and the last stretch is awkward, that stretch is usually the interesting part, and we’re happy to look at it.
Check the troubleshooting list above first. Most first-run failures are a credential that wasn’t set or a Google Sheet whose column headers don’t match. If it’s something else, tell us what the failing node returned and we’ll take a look.
Got one of these running and hit the awkward last ten per cent? Tell us which node is fighting you and we'll give you a straight answer on whether it's worth building properly.
Book a Free Call