# n8n Workflows: How They Work and Examples (2026 Guide) By Priscilla Nakabuye · 2026-10-16 · Source: https://www.activepieces.com/blog/n8n-workflows-how-they-work-and-examples-2026-guide --- Think of an n8n workflow as one trigger plus a chain of connected nodes that pass JSON items along, much as tools like [Activepieces](https://www.activepieces.com) chain steps after a trigger, and each run of it is an execution. An n8n workflow is an automation in the n8n platform that starts with a single trigger, such as a webhook, schedule or app event, and runs through a chain of connected nodes that each fetch, transform or send data, with every run counted as one execution. ## n8n workflows defined: triggers, nodes and executions ![Which triggers start public n8n workflows](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/0cfc704d-d55f-4339-b274-5329d7ce17ef/n8n-workflows-how-they-work-and-examples-2026-gu-fea82cc6.svg "Source: czlonkowski n8n-skills") Facts here were checked on 16 October 2026 against n8n's own pages, except the trigger shares, which come from a community project. ### What a workflow is Before anything else happens, the trigger decides when the workflow starts. Each node after it does one job, such as fetching a record, reshaping fields or posting a message, then hands its output to the next node as JSON items. If you can name the trigger and the three jobs, you have the design. [Activepieces](https://www.activepieces.com) uses the same trigger-then-steps shape, and MoneyGram, Moneypenny, Alan and FundingSocieties run it in production, so the habit transfers. Take one thing from the diagram: the execution is the entire bracketed run, not any single node. It shows one Webhook trigger feeding three nodes, with a small JSON item card passing between each pair, and a bracket over the whole run labelled "one execution", so all three nodes execute as a single unit. ### What an execution is and why it matters Ten nodes cost the same as three each time the workflow runs. That's because an execution is one complete run from trigger to last node, and it's the unit n8n's cloud plans meter, so the number of triggers firing matters more than the number of nodes. Plan around volume: a webhook hit by a busy system can burn through a monthly allowance far faster than the build effort would suggest. In the [czlonkowski n8n-skills](https://czlonkowski-n8n-skills.mintlify.app) breakdown of public workflows: - Webhook triggers start 35%, which means about one in three workflows waits for another system to push an event, and its execution count is set by that system's traffic, not by you. - Schedule triggers start 28%, which means nearly as many run on a clock you control, making their volume predictable and easy to budget. Manual triggers start 22%, typically early-stage experiments that cost nothing until someone promotes them to a schedule, meaning you can keep roughly one in four triggers as free experiments. Service triggers, such as a new row or a new email, start 15%, and they cost one execution per event, which means every incoming event is charged as an execution. ![Activepieces flow builder with a Google Forms trigger configured to capture new responses for a lead-to-CRM workflow.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/650d3b11-4fd5-4575-bd23-2189ca632521/sales-to-customer-success-handoff-automation-gui-284f1958.webp) To see that split in full, look at the chart that follows. ## Building your first n8n workflow You build the workflow from a blank canvas. You add a Webhook trigger that catches a test request, then append a Google Sheets node that writes the caller's email to a row. ![Activepieces workflow builder showing a three-step automation connecting Google Calendar to Gmail with run details and…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/004448b6-4c5a-44ec-a116-431c38d4090f/what-is-tool-calling-how-ai-agents-use-tools-in-22f21aa3.webp) Each stage is a single node, so you can stop and test after any of them. ### Stage 1: open the canvas and create a workflow From the n8n home screen, choose to create a new workflow and give it a name you'll recognise later, such as "Signup to sheet". Naming it now matters because every workflow you leave as "My workflow" becomes one you can't tell apart once a second team starts building. The empty canvas prompts you to add a first step, and that first step is always a trigger. ### Stage 2: add a Webhook trigger and capture test data Add the Webhook node as the trigger and set its method to POST. n8n shows a Test URL and a Production URL. Use the Test URL while building, because it only listens after you click to listen for a test event, and the Production URL only works once the workflow is active. Store the Test URL in a shell variable, start listening, then send a request: ```bash curl -X POST "$WEBHOOK_TEST_URL" \ -H "Content-Type: application/json" \ -d '{"email":"ada@example.com"}' ``` Once the request lands, the node holds real sample data. Look closely at the output: your JSON sits under `body`, not at the top level. That's why the next stage references `$json.body.email` rather than `$json.email`. ![A workflow automation canvas showing a multi-step customer auto-assignment flow with conditional routing and test results…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/1faba18b-1cd1-447d-99e6-b1b1c68ce2fc/private-ai-platform-what-it-is-and-how-it-works-3df0388c.webp) ### Stage 3: write the data to a Google Sheets row Add a Google Sheets node after the Webhook and choose the action that appends a row. Connect a Google credential, then pick the spreadsheet and the sheet tab. Make sure the sheet has a header row, because n8n maps values to columns by header name. In the email column, enter the expression `{{ $json.body.email }}`, then run the node to confirm a row appears. ![A workflow builder showing an AI receipt reader with a Google Sheets Insert Row step selected and its configuration panel…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/bcd0e851-b791-4016-bb1d-99ec1a1bb319/how-to-recover-and-prevent-spreadsheet-overwrite-139fb449.webp) Run a failure on purpose before you trust the build. A run that breaks, such as a revoked connection or a missing column, shows each step's execution time and its input and output JSON, so you can see which node received bad data. To see that layout, open the run view below, with the error and an option to reopen the failed run for editing. ## Activating n8n workflows with error handling Once a test passes cleanly, the next job is switching to the Production URL and activating the workflow. A workflow that only runs the happy path will fail quietly the first week it meets real data, so add branching and error handling before you flip the switch. ### Using IF and Set nodes in n8n workflows Use an IF node to split items into two paths on a condition, and a Set node to rename, trim or reshape fields before they reach the next step. They're the two logic nodes most beginners need, and the public template library backs that up. In the [Pixtex](https://pixtex.dev/research/n8n-node-types.csv) count of public n8n workflows, Set appears in 5,748 templates and IF in 4,937, so copying a template means you'll meet both almost immediately. At 5,931 templates, Code leads, and HTTP Request follows at 5,516, which tells you that most real workflows eventually need a custom script or a call to an API with no dedicated node. Start with IF and Set, and reach for Code only when they can't do the job. 3,718 templates include the optional AI Agent node, ahead of Google Sheets at 3,613, and both are common. That means agents are now mainstream, not exotic, but they add model cost per run. Add one only where a fixed rule can't decide. ### Stage 5: error workflow, activation and production URL Create a separate workflow that starts with an Error Trigger node and sends you a message, then select it under the main workflow's settings as its Error Workflow. Without it, a failed run is visible only if you open the executions list, so a broken credential can go unnoticed for days. Then switch webhooks from the Test URL to the Production URL and toggle the workflow to Active. The Test URL only works while the editor is listening, so any form or app still pointing at it will stop delivering once you close the tab. ![A taped-on temporary doorbell beside a dark house with a visitor at the door.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/eb729c6a-b485-4bd1-a66d-de633e4fbd0f/n8n-workflows-how-they-work-and-examples-2026-gu-75045e44.webp) ### Four example workflows worth copying from the template library Check the last column before you toggle Active. Each row below shows what starts the workflow, which nodes carry it, and which credentials will block activation if they are expired or missing. A credential that worked in testing under your own login may not hold for a scheduled or unattended run. | Example | Trigger | Nodes used | Credentials to check before activating | |---|---|---|---| | Lead capture to Sheets and Slack | Webhook | Webhook, Set, Google Sheets, Slack | Google account access to the sheet; Slack app token and channel permission | | Error alert | Error Trigger | Error Trigger, Set, Slack or Email | Slack token or SMTP login; the workflow selected in settings | | AI Agent triage | Webhook or app trigger | Trigger, AI Agent, chat model, IF | Model provider API key and its spending limit | | Scheduled report | Schedule Trigger | Schedule Trigger, HTTP Request, Set, Email | API key for the data source; SMTP login; server time zone | ![The nodes public n8n templates use most](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/599874a2-ac76-4a4a-b3a8-79eb14d6ea9d/n8n-workflows-how-they-work-and-examples-2026-gu-37774301.svg "Source: Pixtex") With these four running, you've covered capture, alerting, judgement and reporting. That's enough to see where your execution volume will actually come from before you commit to a plan. ## What n8n workflows cost and require For 20 € a month you get Cloud Starter, while self-hosting incurs no licence fee but moves upgrades, backups and security onto your team. Prices reflect n8n's pages as checked 16 October 2026. ### Cloud tiers and the execution allowance Read the maintenance columns before the price column, because the plans differ less in price than in who carries the operational work. | Option | Price | Executions | Active-workflow limits | Upgrades | Backups | Security | |---|---|---|---|---|---|---| | Cloud Starter | 20 €/month | 2,500 | Capped by plan | n8n | n8n | n8n | | Cloud Pro | 50 €/month | 10,000 | Capped by plan | n8n | n8n | n8n | | Self-hosted Community | Licence free; server costs yours | No n8n-imposed cap | No n8n-imposed cap | You | You | You | Moving to Pro at 50 € quadruples the allowance to 10,000 executions, so the jump from Starter is the The text came through as only a fragment ("cheapest capacity you'll buy."), with no competitor, product name, number, or documented fact to preserve. Could you paste the full sentence? I'll rewrite it with the facts intact and the superlative removed. Start from your schedule, because it decides which tier you land on. A workflow running every hour uses about 720 executions a month, so Starter holds three of them. Every five minutes it uses about 8,640, which alone nearly fills Pro. Every minute it uses 43,200, past even Business. If you self-host, there is no licence fee, but the Sustainable Use License limits it to internal business use. Running n8n for your own team is covered; reselling it or hosting it as a service for clients is not. Check that before a department builds on it. Own the server and you own the upgrade schedule, the backups and the patching. Treat it as a standing task with a named owner, because the first guardrail to slip is usually the backup nobody tested. Build the same lead flow in Activepieces and the cost question changes shape. Zapier's pricing page bills per task and Make's bills per module, so both rise with step count, whereas the Activepieces pricing page lists 1 credit per flow run, any number of steps. The three-step lead flow and a thirty-step version draw the same single credit, and the free cloud plan includes 1,000 credits a month with unlimited flows, up to 5 users and no card, so you needn't simplify workflows to stay within budget. The licence question has a file to read instead of terms to interpret: ## Common workflow mistakes and fixes Six mistakes account for most broken first workflows, and each has a fix that takes minutes, not hours. The list below pairs every mistake with its remedy, so a team can check a draft against it before the workflow goes live. - Testing on the test URL and never activating: the test webhook URL only listens while you're watching the editor, so switch the workflow to active and use the production URL before you hand it to anyone. - Loops that inflate executions: build the job so one run handles a whole batch, rather than triggering a fresh run per record. - Hardcoded credentials: store keys in n8n's credential manager so they never sit in node fields or exported files. - No Error Workflow: attach a separate workflow that fires on failure and alerts a named owner. - Ignoring pagination and rate limits: fetch every page, and slow requests down to the limits the API sets. - Unplanned self-hosted upgrades: schedule upgrades, read the release notes first, and test on a copy. ### Volume and execution surprises Close the tab on a webhook that worked perfectly while you watched the editor, and it goes silent, so the first real event is lost. That makes the test-URL mistake the most common first stumble. Activate the workflow, then send a test event to the production URL. On a plan priced per execution, a workflow that fires once per row of a spreadsheet can burn through a month's allowance in an afternoon, and the team that built it usually finds out from the invoice. ![A meter dial maxed out while a long sheet of rows feeds it.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/daf1db5f-ae50-4cc1-94ce-29ec9ae121ea/n8n-workflows-how-they-work-and-examples-2026-gu-75f62953.webp) That is the quieter damage loops cause. Batch the records inside a single run, and estimate monthly runs before you build. For pagination, an API that returns one page at a time will hand a workflow only the first page, and the report looks complete while missing most of the data. Turn on the HTTP Request node's pagination option, and add a wait between calls so rate limits don't reject requests midway. ### n8n credentials and error handling for workflows Paste a key straight into a node and it travels with every export and screenshot, so a single shared workflow can leak access to a whole system. Use the credential manager, and rotate the key in one place when someone leaves. Without an Error Workflow, failures are silent: the schedule keeps running and nobody learns that nothing was delivered. Set one Error Workflow that posts to a team channel, and reuse it across every workflow. Nobody owns upgrades until something breaks, because a self-hosted instance only changes when you change it. Assign an owner, pin the version in your deployment, and read release notes before each update. Run the new version against a backup copy first, so a changed node never takes down a live workflow. ## Running the same lead workflow in Activepieces Rebuild the lead workflow by hand in Activepieces and it comes to three steps: a Catch Webhook trigger, a Google Sheets row, and a Slack message, with both apps among the 741 integrations in the open source monorepo. ![A workflow with three steps: a weekly schedule trigger, a Google Sheets "Get next row(s)" step highlighted in red, and a…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/9c97a633-3fa9-4f11-b113-a673ce77431c/what-is-harness-engineering-building-reliable-ai-31a9d131.webp) If plan and hosting are still the open question, treat it as a pilot: nothing is imported or converted from n8n, so it's not a migration. ### Building workflows with integrations and webhooks Inside Activepieces, flows are built from "integrations", its name for app integrations, roughly 60% of them community-contributed, so the company doesn't directly maintain most of its integration ecosystem. Your first flow uses the webhook trigger, the [Google Sheets piece](https://www.activepieces.com/pieces/google-sheets) to append the lead as a row, and the [Slack piece](https://www.activepieces.com/pieces/slack) to notify the sales channel. Below, the canvas shows that shape: a Catch Webhook trigger, a middle step, and the Slack step selected. In the lead flow the middle step is Google Sheets, where the capture shows a Read Connection action. ![Connections in Builder](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/4bc6de2d-83e7-48de-aa21-0effe60786d2/how-to-automate-the-hr-to-it-handoff-for-new-hir-6d3dd337.webp) In the selected Slack step's panel you'll find fields for Connection, User, Message and Username, and its connection field points back at step 2. That's the habit worth teaching a first team: map each field from the step before it, then press Test Step under Generate Sample Data before publishing. Starting the pilot is cheap for the reasons this article keeps returning to. You're not reading a source-available licence to work out what your use allows, because the core is open source under an MIT licence. On cloud, the plan is free and needs no card, so the first team can test without a purchase order. If hosting is the sticking point, you can self-host instead, and the flow you built on cloud is the same kind of flow you'd run on your own server. ### When staying on n8n is the better choice Stay on n8n if your team already runs production workflows there and they're stable. Rebuilding every flow by hand has a real cost, and a working setup with predictable volume doesn't need a second tool. If you depend on an n8n node that has no matching integration, the same applies. Check the integration list for each app before you commit. If volume, licence terms or hosting are what worry you, build this one flow and compare. [Sign up for Activepieces cloud](https://cloud.activepieces.com/sign-up) and run it for a week; at 1 credit per run, the free plan's 1,000 monthly credits cover 1,000 leads. ## Frequently asked questions ### Licensing and sharing **Is n8n free to use for business workflows?** Yes for internal business use on a self-hosted install, because n8n's source is available under its Sustainable Use License rather than a standard open-source one. The cloud product is paid, and the license limits reselling n8n or hosting it as a service for others. Client work is covered only if clients cannot create or edit the workflows. Clients can't open the editor on your instance, so check the license text before you build for them. **Can n8n workflows be exported and shared as JSON?** Yes, any workflow downloads as a JSON file, and you can copy nodes between instances by pasting. Credentials stay behind, so each recipient reconnects their own accounts. That makes exported workflows workable as templates. In a rollout, the share of new workflows started from a template is one of the easiest adoption measures to track. ### Limits and skills **How many workflows can one n8n instance run?** There's no fixed workflow count, because the real limits are execution volume, the memory on the server, the payload size each run carries, and the execution timeout. Two chatty workflows can strain a small server more than fifty quiet ones. Size the server on expected runs, not on how many workflows you plan to build. **Do I need to code to build an n8n workflow?** No, a workflow is a trigger followed by nodes you configure in the editor. Code becomes useful when you reshape data in ways the built-in nodes don't cover, and the Code node is there for that. In most rollouts, the team that hits a wall is the one whose data is messy, not the one that can't code. ### Getting started **What should I do on Monday to start with n8n?** Run a small pilot with one owner and one workflow. 1. Pick one repetitive task that one team already does by hand. 2. Estimate how often it will run, since volume decides your plan and server size. 3. Read the license terms and decide where it will be hosted. 4. Build the trigger and nodes, then test with real but low-stakes data. 5. Export the working version as JSON and keep it as the template for the next team. ## Related reading - [Zapier ChatGPT Integration Tutorial for Beginners](https://www.activepieces.com/blog/how-to-use-zapier-with-chatgpt-examples-included) - [Best AI Agent Platforms for Workflows: 2026 Guide](https://www.activepieces.com/blog/best-ai-agent-platforms-for-workflows-2026-guide) - [HR Agent Guide: How AI Agents for HR Improve Workflows](https://www.activepieces.com/blog/ai-agents-for-hr) ## References - [czlonkowski n8n-skills](https://czlonkowski-n8n-skills.mintlify.app) - [Pixtex](https://pixtex.dev/research/n8n-node-types.csv) - [n8n](https://n8n.io/limitless-integrations/)