Build an n8n workflow: your first one step by step
Triggers, nodes, connections – every n8n workflow is made of these three parts. This guide builds a first flow with you, from a form to your CRM, explains the building blocks on that real case and ends with when to build it yourself and when help is faster.
What is an n8n workflow?
Before you start clicking, a clear picture of the structure helps. A workflow in n8n is a chain of building blocks that runs a process on its own. It begins with a trigger, moves through several nodes and ends where the result is needed – in the CRM, in an email, in a spreadsheet. Once these three terms make sense, you can build your first workflow.
- n8n workflow
- An n8n workflow is a visually assembled automation: a trigger starts the flow, connected nodes handle the individual steps, and the connections between them define the order. n8n connects the tools you already use through their interfaces.
Triggers, nodes and connections
The trigger is the starting point. It decides when a workflow runs: on an incoming webhook, at a fixed time, when a new row appears in a spreadsheet. Without a trigger nothing happens – it is the condition under which the rest even starts.
A node is a single step of work. There are nodes for concrete tools (CRM, mail, database) and for logic: check, transform, filter, branch. Each node receives the data from the previous one, does its one thing and passes the result on.
The connections are the lines between the nodes. They set the path of the data and therefore the order. A flow can split – one branch for business customers, one for private requests – and merge again later. This is exactly where the logic lives that turns single steps into a process.
If you want to see what this produces in real projects, you'll find six worked-out flows in the n8n use cases.
Build your first workflow in six steps
The fastest way to understand n8n is on a concrete case. We build the classic one: a request from the contact form should be checked, routed and created as a contact in the CRM – without anyone typing it out. Here's how:
Every workflow starts with a trigger. For our example – a form submission should reach the CRM – you use a webhook trigger. n8n gives you a URL that you set as the form's target. From now on, every submission lands directly in n8n.
A node is one step of work. You click the plus behind the trigger and pick the node for your target app, here the HubSpot or CRM node. The first time, you store the credentials once – after that n8n knows the connection.
This is the core. The fields from the form (name, email, message) have to be mapped to the fields in the CRM. In n8n you drag the values from the trigger data into the node fields. Where a field is missing or needs renaming, a Set node in between helps.
Not every request should be handled the same way. With an IF node you check, for example, whether a business email is present and send the flow down two paths. That's how you learn early how a workflow branches instead of just running straight through.
n8n runs the workflow on demand with a sample submission and shows you, after each node, what comes in and what goes out. Here you catch typos in the mapping and empty fields before anything reaches the CRM. Only once a run is clean do you move on.
The switch at the top right takes the workflow live, and from now on it reacts to every real request. For the first few days you check the execution history: it logs every run and flags errors, so you can see whether everything really arrives.
Is the effort worth it?
The build costs time once, running it costs almost nothing. Whether it pays off depends on how often the flow happens. A small example for our form workflow, deliberately run as a scenario:
Have a flow in mind but aren't sure it's a good first workflow? Describe it to me briefly – I'll tell you honestly where the best starting point is.
Describe your flow →Build it yourself or have it built?
A simple workflow is well within reach yourself, and the first success is motivating. But once a flow becomes business-critical, connects several systems or has to be properly guarded against errors, the gap between "works in the test" and "runs reliably day to day" becomes noticeable. This breakdown helps you decide:
Build it yourself when
- The flow runs across two or three standard tools with ready-made nodes
- A failure does no real harm and you can test in peace
- You want to learn n8n and have time to experiment
- The volume is small and the flow rarely changes
Help saves time when
- The workflow is business-critical and has to run fail-safe
- Data fields without a ready node need to be mapped to each other
- An API has to be connected for which no block exists
- The flow should be monitored, maintained and looked after over time
If you're at that boundary, an outside look is often cheaper than a workflow that quietly loses data. How that kind of collaboration works is covered in the n8n consulting guide. If the finished workflow should run permanently, you'll find more on hosting and maintenance under managed n8n hosting. The full scope of work is bundled on the n8n agency page.
The most common beginner mistake is a workflow without a safety net: if a tool goes down briefly or an empty field comes in, the whole flow breaks – often unnoticed. Plan from the start what should happen on an error: a retry, a notification, an entry in an error list. A workflow that reports problems instead of swallowing them is worth more than one that only works in the ideal case.
Common questions about building workflows
I taught myself to code at 18 and today build workflows in n8n and HubSpot for companies. This guide is the path I also take in a first session with clients: get one small, real flow running cleanly, then build on it. Once the workflow runs permanently, I take on hosting and maintenance on request.
Auf LinkedIn vernetzen →Where is your best first workflow?
30 minutes, no strings attached. We look at a concrete flow at your company, and you get an honest read on whether to build it yourself or have me do it. Operation and maintenance are available on request.
Termin auswählen →