n8n | Apporo

n8n

Automate the boring parts, one workflow at a time

Hand out one URL and let the outside world start your workflow

Hand out one URL and let the outside world start your workflow

Every trigger so far has been n8n making the move: you press a button, a clock strikes, or n8n goes out and asks a service whether anything is new. This part turns the arrow around. A form is submitted, a LINE bot receives a message, a door sensor trips, someone pushes to GitHub — all of it reaches n8n through the Webhook node. It is also the last part of the series, so stay to the end.

Sep 9, 2026 n8n

Every node so far follows rules. This one makes a decision.

Every node so far follows rules. This one makes a decision.

A customer types a question you did not anticipate. An email hides an amount and a date inside a sentence. Neither of those is an IF condition you can write in advance. The AI Agent node puts a language model inside your workflow and lets it decide, on its own, which of the tools you attached it should reach for. This part builds a working chatbot in seven steps, hangs a Google Sheet off it, and p

Sep 9, 2026 n8n

The ten percent no ready-made node can do: the Code node

The ten percent no ready-made node can do: the Code node

Fourteen parts in, most of what you build is a core node wired to an integration node. Then a job turns up that none of them fit: orders that have to be regrouped along two dimensions at once, an API response buried three levels deep, a top-three ranking by share of revenue. The Code node is the escape hatch n8n gives you for exactly that — a blank JavaScript editor with items going in and items c

Sep 9, 2026 n8n

The same four nodes in five workflows: pull them into a sub-workflow

The same four nodes in five workflows: pull them into a sub-workflow

You have copy-pasted the same run of steps into five workflows. One small change now means five edits, and you are never quite sure you got them all. This part shows you how to lift shared logic out into a workflow of its own, call it from everywhere else with one node, and change it in a single place from then on. It is a function call, drawn on a canvas.

Sep 9, 2026 n8n

Reshape the data between two nodes without writing a line of code

Reshape the data between two nodes without writing a line of code

The node upstream hands you a large blob of JSON. The node downstream wants three fields out of it, renamed, combined, and with a default filled in where one is missing. That gap is where beginners reach for a Code node and where they do not need to. The Set node — called Edit Fields (Set) in the newer interface — is the visual tool built for exactly this job, and learning it properly is what keep

Sep 9, 2026 n8n

A workflow that fails at three in the morning, and tells you so

A workflow that fails at three in the morning, and tells you so

Everything you have built so far runs when you press the button and you watch it work. The moment a workflow goes Active on a schedule, that stops being true — it runs while you are asleep, and when it dies it dies quietly. This part strings a net under it: an error workflow that messages you when a run gives up, a node-level retry that rescues the failures that were only ever momentary, and the W

Sep 9, 2026

Splitting a workflow in two, and putting it back together

Splitting a workflow in two, and putting it back together

Everything so far has been a straight line: data arrives, each node hands it to the next. Real automations are not like that. An order over 1,000 goes to the manager and the rest go on a list. Five hundred rows have to reach an API that allows five calls a second. Two branches finish separately and you want one notification at the end. This article covers the nodes that split a path, and the nodes

Sep 9, 2026

Permission to act as you, and a value to act on

Permission to act as you, and a value to act on

You have wired up Slack, Gmail and Google Sheets. Two questions were never answered properly. What gives a workflow the right to send messages and write spreadsheets as you — that is the credential, one set of account authorization details n8n keeps encrypted. And how does a node put yesterday's order number into today's message — that is the expression, a short piece of code inside {{ }} that n8n

Sep 9, 2026

The node that reaches every API n8n has never heard of

The node that reaches every API n8n has never heard of

Part 8 wired up Slack, Gmail and Google Sheets — popular products that each ship a ready-made node, so you fill in a few fields and they work. The world holds a great deal more than those. The CRM you have to connect at work, a regional accounting system, an IoT vendor's API: n8n may have no node for any of them. This article is about the one node that does not care. If the other side has a REST A

Sep 9, 2026

Slack, Gmail, Google Sheets and Drive: the four nodes most office requests are made of

Slack, Gmail, Google Sheets and Drive: the four nodes most office requests are made of

Ask around an office for a week and the automation requests keep naming the same four services. A Slack message when a customer signs up. A Gmail thank-you when a form comes in. A row in Google Sheets every night. A customer's upload filed into its own folder on Google Drive. This article covers the operation you will actually use from each node, the credential each one needs, the trap each one hi

Sep 9, 2026

What travels between nodes, and what makes a workflow start

What travels between nodes, and what makes a workflow start

Two questions account for most of the confusion in a beginner's first week. Why did the Slack node send a hundred messages when I only asked for one? And why has my 8:00 schedule not run once all week? Both have short answers. The first is the item — the unit of data that moves from one node to the next, one row at a time. The second is the trigger — the node at the front that decides when any of

Sep 9, 2026

Your first workflow: today's calendar in Slack, every morning at eight

Your first workflow: today's calendar in Slack, every morning at eight

Everything so far has been reading — other people's templates, other people's workflows, the four families a node can belong to. This part is the first time you start with an empty gray grid and finish with something that runs without you. At 8:00 every morning, n8n reads today's Google Calendar and drops the titles and times into your Slack. Three nodes do it. And the shape those three nodes make

Sep 9, 2026

1
2