EN
Ihor Nikolenko- Four Words That Make n8n Click
- Where to Run It: Cloud or Self-Hosted
- Your First Workflow: Lead → Spreadsheet → Telegram
- Five Techniques to Keep a Workflow From Breaking in a Week
- What to Build Next
- Common Beginner Mistakes — and How to Avoid Them
- When You Need Someone Who's Already Done This
- The Short Version
- Frequently Asked Questions
A lead comes in from the website, straight to your inbox. You copy it into a spreadsheet. You message the manager on Telegram: "new one just came in." The manager asks, "which one?" You forward it. A week later, the spreadsheet doesn't match the inbox, two leads have gone missing, and nobody knows whose fault it is. This isn't a people problem. It's work a machine should be doing, and instead you're doing it yourself — every day, five minutes at a time, which add up to hours.
n8n is the tool that takes this work off your hands. It's often described as "for developers," and that scares people off. In reality, a developer is only needed for complex workflows, and the first and most useful ones — "it arrived → log it → notify someone" — get built with a mouse in an evening, once you understand a handful of concepts. I use n8n in my own projects and in the club, and those are exactly the concepts I start with, with anyone who wants to automate without code.
This guide is for an owner or manager with no technical background: what a node, a trigger, and a workflow are, where to run n8n, how to build your first working workflow step by step, how to keep it from breaking a week later, and where to grow from there.
Four Words That Make n8n Click
Workflow is a chain of steps that runs automatically. "When a lead comes in → log it in a spreadsheet → send a notification" is one workflow.
Node is one step in the workflow. Every node does one thing: reads a spreadsheet, sends a message, checks a condition. Nodes connect with arrows, and data flows along those arrows from left to right.
Trigger is the special first node that starts the workflow. A trigger can be an event (a new lead, a new Telegram message, a new email), a schedule (every day at nine), or an incoming request to a webhook address.
Data is what gets passed between nodes. In n8n, that's a set of fields: name, phone number, message text. Every downstream node sees the previous node's fields and can use them.
That's it. Everything else is just the names of specific nodes for specific services, and you don't need to memorize them — you look up the one you need in the list when you need it.
Where to Run It: Cloud or Self-Hosted
n8n gives you two ways to run it, and for a non-technical person the choice is simple.
n8n Cloud is a ready-made service at n8n.io: you sign up and start building right away. There's nothing to install, and updates and backups are handled on the service's side. Cloud pricing is based on the number of workflow executions, not on each internal step, which is an important difference from some other platforms, where a long workflow costs more than a short one.
Self-hosted means n8n gets installed on your own hosting via Docker. The license allows this for free for a business's internal use, your data never leaves your server, and the only limit on executions is the machine's capacity. The cost is a bit of technical know-how up front, or one hour of a specialist's time to set it up and show you how to update it.
| Criterion | n8n Cloud | Self-hosted |
|---|---|---|
| Getting started | Sign up, start building right away | Install via Docker |
| Updates and backups | Handled by the service | You or your specialist |
| Cost | A plan based on execution count | Just the server; the license is free for internal use |
| Where the data lives | With the service | With you |
| Best for | First workflows, a team with no in-house tech person | Many workflows, personal data, full control |
My advice: start in the cloud. Once you have more workflows than fingers on one hand, and you've realized this is here to stay, move to your own server; n8n supports exporting and importing workflows, so the move isn't "starting from scratch."
Your First Workflow: Lead → Spreadsheet → Telegram
Let's build exactly the workflow this article opened with. It's useful right away, and it demonstrates every basic technique.
- Trigger: a form. Add an n8n Form Trigger node. It builds a simple form on its own, with whatever fields you define: name, phone, comment. Once saved, n8n gives you a form URL — you can embed it on your site or share it as a link. If your site already has a form, use a Webhook node instead: your site sends the lead straight to its address.
- Log it to a spreadsheet. Add a Google Sheets node with the "append row" action. The first time you connect it, n8n will ask permission to access your Google account — this is called credentials, and it's saved once for every workflow. Pick your spreadsheet and sheet, and for each row field, specify where the value comes from: n8n shows you the fields from the form, and you just drag them into the right cells.
- Notify the manager. Add a Telegram node with the "send message" action. This needs a bot: open BotFather in Telegram, create a bot with the /newbot command, and grab the token — that becomes the node's credentials. Add the bot to the managers' chat and set that chat as the recipient. Build the message text from the fields: "New lead: name, phone, comment."
- Test it. Click "Execute workflow," fill out the form with test data, and watch how the data moves through the nodes: n8n shows you the contents at every step. A row shows up in the spreadsheet, the message arrives — the workflow works.
- Turn it on. Flip the "Active" toggle in the top corner, and the workflow now runs without you.
Three nodes, one evening, and a task that used to take five minutes every day is gone. Next come the techniques that make a workflow reliable.
Five Techniques to Keep a Workflow From Breaking in a Week
Conditions. An IF node splits the flow into two branches based on a rule: if the comment contains the word "urgent," notify the manager personally instead of the general chat. Rules are built with a mouse: a field, a condition, a value.
Expressions. Sometimes you need to do more than drop in a field — you need to tweak it a bit: combine a first and last name, add today's date, strip spaces from a phone number. In n8n these are expressions in double curly braces — {{ }} — with built-in hints. You don't need to learn a language: most of what you need is already in the hints, and any AI assistant can write the rest if you describe the task in plain words.
Retries on failure. Every node's settings include "Retry On Fail": if Google doesn't respond for a second, n8n tries again instead of dropping the lead.
An error workflow. A separate, small workflow with an Error Trigger that sends you a Telegram message saying "workflow X failed at step Y." In the main workflow's settings, you set this as the Error Workflow. It's your main safeguard: you find out about a problem immediately, before the customer notices anything.
Notes. The Sticky Note node is a yellow note pinned to the canvas. Write down what the workflow does and why each branch exists. In a month you'll have forgotten, and a colleague will never have known in the first place.
What to Build Next
Once the first workflow has run trouble-free for a week, the appetite kicks in. Here are the next three I recommend, in exactly this order.
Scheduled reminders. A Schedule trigger reads the leads spreadsheet every morning, finds the ones without a "contacted" mark that are more than a day old, and sends the list to the chat. It's discipline without having to nag anyone.
A two-way Telegram bot. A Telegram Trigger reacts to messages sent to the bot. A customer writes to the bot — the workflow asks clarifying questions, logs the answers, and hands the manager a ready-made summary. I write a separate guide about a lead-qualifying bot like this; a ready-made foundation for it is the n8n Telegram Traffic Processor, a workflow that takes in Telegram traffic, processes it, and passes it along.
A language model inside. OpenAI, Anthropic, or Google nodes inside the workflow read the lead's text and return structured output: topic, urgency, a draft reply. This isn't "log it and notify" anymore — it's "understand it and prepare a response." But only after the simple workflows are running reliably.
There's a whole library of ready-made templates on the n8n site for all of this: you import the entire workflow and just plug in your own credentials and spreadsheets. Someone has already done half the work for you.
Common Beginner Mistakes — and How to Avoid Them
- One giant workflow for everything. Five small ones, each with a single job, are better. They're easier to check, and one breaking doesn't stop the others.
- Testing on real data. The first run should hit a test spreadsheet and a test chat. A workflow that fires off a message to a hundred real customers because of a bad condition has actually happened to every team that skipped this step.
- No error workflow. A silent failure is the most expensive kind. Set up the Error Workflow before you even build your second workflow.
- Credentials in chat. Bot tokens and keys stay inside n8n, never in a conversation. A leaked token means someone else has access to your bot.
- Automating a process that isn't settled yet. If you yourself don't know how a lead is supposed to be handled, a workflow will just lock the chaos in place. Do it by hand for a week first, then automate.
When You Need Someone Who's Already Done This
Everything in this guide, you can do yourself. The line where it's worth bringing in someone experienced is when the number of workflows grows large, when you're connecting systems with no ready-made node, when customers' money is on the line, or when you're migrating n8n to your own server. There, one hour of an experienced person's time saves a week of searching.
If you want to learn this systematically, with practice and feedback instead of scattered videos, the Evolve.Place Academy has courses with mentors, and n8n automation is one of the tracks I recommend a business owner start with. It's the kind of training that leaves you with workflows that actually run, instead of a browser tab labeled "try this someday."
The Short Version
- A workflow is a chain of nodes; a trigger starts it via an event, a schedule, or a webhook; data flows along the arrows.
- Start with n8n Cloud, move to a self-hosted server once you have many workflows; export and import make that possible.
- First workflow: Form Trigger → Google Sheets → Telegram. Three nodes, one evening.
- Reliability: IF for conditions, expressions for small transformations, Retry On Fail, an Error Workflow, notes on the canvas.
- Next steps: scheduled reminders, a two-way Telegram bot, a language model inside the workflow.
- Many small workflows beat one big one; test on test data; keep tokens inside n8n only.
- Only automate a process that's already settled: do it by hand for a week first.
Frequently Asked Questions
Do I need to know how to code?
Not for the workflows in this guide. Expressions in curly braces are the most you'll need, and n8n itself or any AI assistant can help you write them. Code is needed for non-standard data transformations, and there's a separate node for that which not everyone ever touches.
How is n8n different from Make and Zapier?
The main differences are the ability to self-host and a pricing model based on workflow executions instead of individual steps. I go through a detailed comparison of all three platforms in a separate article.
Is it safe to give n8n access to a Google account and a CRM?
In the cloud, your data is stored by the service under its own policy; self-hosted, it stays with you alone. Either way, create separate, limited-permission accounts for your automations — your personal admin account isn't the right choice for this.
What do I do if a workflow stops working after a service update?
Most of the time, the credentials have expired or the service changed its interface. The Error Workflow will let you know right away; re-authorizing takes a minute. That's exactly why the error workflow gets set up first.
