When most people hear AI automation, they imagine a mess: overpriced consultants, half-baked integrations, and workflows that break the second you turn your back.

Honestly, I thought the same when I first dipped into it. Automation looked intimidating. But the funny part? Once you actually start building, you realize most of it boils down to a few repeatable building blocks.

Think LEGO, not rocket science.

This clicked for me when I read Manthan Patel’s LinkedIn post, where he broke down n8n’s seven essential nodes. Around the same time, I stumbled across Alex Pobeditel’s post, which took the opposite stance: “n8n is dead—RIP.”

Two perspectives. Both valid. And they reflect exactly where we are in 2025: automation is exploding, the tools are shifting, but the fundamentals are the same.

The Canadian Context: Automation Isn’t Optional Anymore

Let’s zoom out for a second. This isn’t just a Silicon Valley playground—it’s happening here in Canada too.

• 12.2% of Canadian businesses reported using AI to deliver products or services last year. That’s double the rate from the year before. (StatsCan)

• 70% of SMBs in Canada using AI say it improved efficiency and productivity. (Microsoft Canada)

• The Canadian RPA (Robotic Process Automation) market is projected to grow nearly 7x by 2030. (Grand View Research)

If you’re running a business today and you’re not thinking about automation—you’re not just behind. You’re standing still while everyone else is moving forward.

The 7 Building Blocks of Automation

So let’s talk about those building blocks.

According to Manthan, n8n has seven core nodes that cover ~95% of what you’ll actually automate. And after using them myself, I have to agree.

Here’s the toolkit:

1️⃣ Code Node

Your “escape hatch.” When a connector doesn’t do what you need, you can drop in a little JavaScript or Python.

• Example: Convert JSON to XML before pushing data into a legacy CRM.

  👉 Docs

2️⃣ HTTP Request

APIs are the veins of automation. This node is your IV drip.

• Example: Pull data from Apify and push leads into Slack.

  👉 Docs

3️⃣ Edit Fields

Data rarely comes in the shape you want. This node cleans it up.

• Example: Standardize “first_name” into “nombre” for international teams.

  👉 Docs

4️⃣ IF Node

The simplest form of decision-making: if this, then that.

• Example: Active customers get routed to account managers; inactive ones into re-engagement campaigns.

  👉 Docs

5️⃣ Switch Node

Think of this as the IF node’s older sibling. Instead of two choices, it gives you many.

• Example: Route 200/404/500 API responses differently.

  👉 Docs

6️⃣ Loop Over Items

Perfect for repetitive tasks.

• Example: Send 100 personalized onboarding emails—one at a time, so you don’t overwhelm your server.

  👉 Docs

7️⃣ Error Handling

Not technically a node, but a lifesaver. Without it, your workflows will break silently.

• Example: Retry failed API calls, send Slack alerts, or reroute tasks automatically.

  👉 Docs

These seven cover so much ground it’s almost unfair. HR, finance, ops, product—you name it.

Real-World Examples (Beyond Sales)

Most people first meet automation through sales or lead gen. But these same nodes can run almost any part of your business.

• HR: Auto-provision accounts, handle onboarding checklists, notify managers.

• Finance: Process invoices, reconcile payments, send reminders.

• Operations: Sync inventory, flag low stock, trigger supplier orders.

• Customer Success: Route tickets instantly, send surveys after resolution.

• Product/Engineering: Monitor error logs, generate bug reports, trigger CI/CD tasks.

I worked with one SMB that used these nodes to pull weekly reports from 4+ different tools, standardize the formats, flag anomalies, and send a summary dashboard every Monday morning. What used to take five hours of manual exports now happens before the team even opens their laptops.

The Debate: Is n8n Outdated in 2025?

Here’s where Alex’s point comes in.

He argued that n8n is basically obsolete now. And if you’ve spent hours debugging expressions, you probably sympathize.

• Workflows can break in unpredictable ways.

• Templates often don’t work out of the box.

• Debugging connectors eats up time you’d rather spend elsewhere.

Meanwhile, AI-native tools like Cursor or Claude Code are stepping up. You can describe a business process in plain English and get a working app scaffolded in minutes. That’s a game-changer.

So yeah, I get why some are declaring “RIP n8n.”

My Take: Why n8n Still Matters

But here’s the thing: the building blocks haven’t changed.

APIs still need connecting.

Data still needs cleaning.

Processes still need error handling.

Learning automation in n8n is like learning to drive stick. Sure, you’ll eventually want an electric on autopilot. But understanding the mechanics makes you a better driver—no matter what you’re sitting in later.

Or to put it another way:

Tools come and go. Fundamentals stay with you.

That’s why I don’t think n8n is “dead.” It’s becoming more of a training ground—a visual way to learn the fundamentals before jumping into AI-driven tools.

Wrapping It Up

In 2023, n8n was the scrappy tool for no-code automation.

In 2025, it’s getting challenged by shinier, AI-native players like Cursor, Claude Code, and Lovable.

But fundamentals don’t expire. Whether you’re in Zapier, Make, n8n, or the next big AI-first tool—you’ll still find yourself using the same seven building blocks.

So the real question isn’t “Is n8n dead?”

It’s “Do you know automation well enough to adapt—no matter what tool wins?”

👉 Over to you: are you still building with n8n in 2025, or have you already made the jump to AI-first tools?