Pipewave LogoPipewave
n8n in practice

n8n use cases: real-world workflow examples

What you can automate with n8n doesn't show in a feature list, it shows in concrete processes. This page walks through six workflows I've built in real projects – from CRM sync to reporting, each with the effort behind it and what it actually takes off your plate.

Discuss your own workflowfree intro call, about 30 minutes
Workflow
TriggerForm / schedule
n8nLogic & mapping
CRMContact & deal
EnrichmentCompany data
Slack / mailAlert

What can you automate with n8n?

In short: any process where someone currently moves data between two programs by hand. n8n is a workflow engine that connects your tools through their APIs and holds the logic in between – when a lead comes in, then check, enrich, create, notify. The six examples below aren't invented scenarios but patterns that occur in almost every company.

One note up front: n8n isn't always the right choice. If a process stays entirely within one system, a native automation is often simpler. But as soon as several tools work together, n8n earns its place. Why I use n8n rather than Zapier or Make is covered in the tool comparison. If you're just starting out, the guide to building your first n8n workflow walks you through the setup step by step.

Workflow 1

Keep two systems in sync

A shop, an ERP and a CRM each keep their own version of the same customers. Change an address in the ERP and the CRM knows nothing about it, so sales writes to the old one. An n8n workflow reconciles the two systems on a fixed schedule or on every change: it reads the changed record, maps the fields onto each other and writes it into the target system – in one direction or both.

The effort sits in the mapping: which field matches which, and who wins on a conflict? Once that's settled, the sync runs quietly in the background. How I connect HubSpot to other systems in detail is covered in the guide on the n8n HubSpot integration.

Workflow 2

Lead routing from the form

A contact-form enquiry is the moment where manual work is most expensive – because time passes before anyone reacts. This workflow picks up the enquiry at once and performs the four steps someone would otherwise do by hand. Here's how the process looks in detail:

01
Trigger: new lead

A form on the website is submitted. n8n catches the data through a webhook before it lands anywhere by hand.

02
Check and enrich

n8n matches the email against the CRM (duplicate?), pulls the company's industry and size from a source such as its website or a register, and fills in the missing fields.

03
Score and assign

Based on your criteria the lead gets an initial rating and is routed to the right person in sales. If it doesn't fit, that gets flagged instead of quietly waved through.

04
Create and notify

The contact lands in the CRM fully sorted, and the responsible person gets a short message in Slack or by email – with the context they need to follow up.

The payoff is twofold: sales finds pre-sorted leads with context, and no one has to watch a form inbox. The effort sits in defining the criteria and connecting the enrichment source – after that every lead follows the same clean path.

Workflow 3

Enrich contacts automatically

A new contact arrives with a name and email, nothing more. Industry, company size and location are missing for scoring. Instead of someone researching that, an n8n workflow pulls those details from a data source, checks them for plausibility and writes them into the right fields. Uncertain matches it flags for review rather than adopting them blindly.

The point where such a workflow fails is rarely the technology, but the data quality of the source. How I set up enrichment cleanly and where its limits lie is covered on the page about CRM data enrichment.

Recognise one of your own processes in these examples? Describe it to me in a line or two – I'll tell you honestly whether an n8n workflow is worth it.

Describe your process
Workflow 4

Notifications on important events

Some things must not get lost in an inbox: a deal crosses a certain amount, a long-quiet customer gets back in touch, a payment fails to arrive. An n8n workflow watches for such events and sends the right person a short, context-rich message in the right channel – in Slack, by email or as a task in the CRM. No constant staring at a dashboard, just a signal exactly when it matters.

The appeal is that such a workflow starts small and grows easily: one rule first, then a second. The only thing that matters is getting the threshold right, otherwise helpful alerts quickly turn into noise that no one reads any more.

Workflow 5

Recurring reporting

Every Monday the same chore: copy numbers together from the CRM, the shop and an analytics tool, pour them into a spreadsheet and send the report. An n8n workflow pulls the values from each source via API, adds them up and files the finished report or sends it straight to the distribution list – on time, in the same format, with no copy-and-paste errors.

Beispielrechnung

Weekly report: manual vs. automated

Annahmen
Reports per month
4
Time per report (manual)
90 min
Internal hourly rate
€40
n8n running cost
€7/mo
Rechnung
Manual effort6 hrs/mo
Cost manual€240/mo
Cost automated€7/mo
Saving per year≈ €2,800

Example calculation, deliberately marked as a scenario. Values vary by number of sources and data quality – for orientation, not a guarantee. The one-time build is not included here.

Workflow 6

n8n plus an AI agent

The first five examples follow fixed rules. As soon as a step needs judgement, a language model joins in: an incoming email isn't just forwarded but read, classified and given a draft reply. n8n stays the frame that connects the tools and controls approval; the model takes on the part that used to need a person. That turns a rigid workflow into one that also handles text and unclear cases.

The boundary still matters: the agent proposes, a human approves, as long as sensitive steps are involved. How such agents are built and safeguarded is covered on the page about AI agents for companies.

Don't start with the hardest workflow

The first workflow costs the most time, every next one less. Start with a process that happens often, is clearly defined and does no harm if it errs. A visible success convinces the team more than a big concept – and you get to know your systems before critical processes follow.

Common questions about n8n workflows

Anything where someone currently carries data back and forth between two tools by hand: moving form submissions into the CRM, enriching contacts, keeping two systems in sync, alerting the team on important events or assembling recurring reports. n8n connects the tools you already use via their APIs and holds the logic in between.
JK
Über den Autor
Joshua Kresse
Gründer von Pipewave · Automatisierung & KI

I taught myself to code at 18 and have since built a series of these workflows with n8n and HubSpot. The examples here come from real projects – including the cases where a native automation turned out to fit better than an n8n workflow. When a process needs to run long-term, I also take care of hosting and maintenance.

Auf LinkedIn vernetzen
Diese Woche 3 Slots frei

Which workflow fits your company?

30 minutes, no strings attached. We look at one concrete process on your side, and you get an honest read on whether and how an n8n workflow pays off. I'll handle running and maintaining it too if you want.

Termin auswählen
Kein Verkaufsgespräch · Antwort in 24 h