n8n workflows: three simple examples and what they cost in executions

An n8n workflow is a chain of nodes started by a trigger: a submitted form, a set time, a new email. n8n Cloud does not bill nodes. It bills executions, meaning complete runs. The three examples below (form to spreadsheet and email, monitoring, email triage) use 200, 720 and at most 900 executions a month under our assumptions, or about 1,820 in total.

How n8n counts executions, trigger by trigger

The whole calculation rests on the trigger. The docs give one rule per type.

What starts the workflow	What counts toward the quota
Schedule Trigger (set time or interval)	One execution every time it fires, whatever the outcome
Polling node, which checks at regular intervals for something new	One execution only when new data is found
Webhook	One execution per incoming request, even with an empty body
A run started by hand from the editor	Nothing
Sub-workflow called by another workflow	Nothing extra: only the parent execution counts
Error workflow	Nothing

n8n docs, “Understand executions” (accessed November 11, 2026)

The examples that follow are our own: common use cases, described with standard n8n nodes. They don’t copy any template from the vendor’s library, and the volumes are assumptions for you to replace with yours.

Example 1: form to spreadsheet and email

The need. Every quote request should be logged in a spreadsheet, confirmed to the customer by email and flagged to the team.

The nodes.

1. n8n Form Trigger: a form hosted by n8n. If the form already lives on your website, a Webhook node receives its data instead.
2. Google Sheets: appends a row with the name, email and request. n8n docs, “Google Sheets” (accessed November 11, 2026)
3. Send Email: sends the confirmation to the customer.
4. Send Email (or a team chat node): alerts whoever handles quotes.

The count. One form submission starts the workflow once: one execution, whether the workflow has four nodes or twelve. With 200 requests a month, that is 200 executions. The table in the docs does not name the Form Trigger; we apply the general rule for production executions, which are started automatically by a trigger.

For comparison, a tool that bills every step, trigger included, would count four units per request here, or 800 a month. That gap is the subject of the guide to billing units.

Example 2: monitoring a news feed

The need. Watch a site’s RSS feed (a competitor, a government agency, a tech blog) and get the articles that mention a keyword by email.

Version A, on a schedule.

1. Schedule Trigger: fires every hour.
2. RSS Read: reads the feed.
3. If: keeps only the articles that contain the keyword.
4. Send Email: sends the matching articles.

The count. The Schedule Trigger counts one execution every time it fires, even when the feed has nothing new. Every hour means 24 a day, or 720 executions in a 30-day month. The interval setting changes everything:

Interval	Executions per month
Once a day	30
Every hour	720
Every 15 minutes	2,880
Every 5 minutes	8,640

Version B, with polling. The RSS Feed Trigger node replaces the first two nodes: it checks the feed at the interval you choose and starts the workflow only when a new item has been published. Under the official rule, a check that finds nothing doesn’t count. For a feed that publishes five articles a day, that is at most 150 executions a month, however often it checks. n8n docs, “RSS Feed Trigger” (accessed November 11, 2026)

Example 3: triaging incoming email

The need. Sort the messages that reach a shared inbox (sales, support, billing), label them and alert someone when a request is urgent.

The nodes.

1. Gmail Trigger: checks the inbox at the interval you choose and picks up unread messages only.
2. A sorting node: either simple rules (a Switch node on the sender or subject), or an AI model that reads the message and picks a category, for example with the AI Agent node.
3. Gmail: adds the matching label.
4. Send Email (or a team chat node): raises the alert for the urgent category.

The count. The Gmail Trigger is a polling node: only checks that find a new message count. With 30 emails a day, that is at most 900 executions a month. It will be fewer if several messages arrive between two checks: according to its docs page, the node handles up to 10 per poll by default, in the same execution. n8n docs, “Gmail Trigger” (accessed November 11, 2026)

If you use an AI model. The workflow run still counts as one execution, but the model calls are paid on top: with your own provider keys, or with Gateway credits on the Cloud Starter and Pro plans. The guide to automating email replies with AI covers that case.

The total, against the quotas

Workflow	Assumption	Executions per month
Form to spreadsheet and email	200 requests	200
Monitoring, scheduled version	Every hour	720
Email triage	30 messages a day	900 at most
Total		About 1,820

The entry plan on n8n Cloud, Starter (€24 per month), includes 2,500 executions: these three workflows fit. Move the monitoring workflow to a 15-minute interval and the total climbs to 3,980: you then need the Pro plan (€60 per month for 10,000 executions), or version B of the monitoring workflow, which brings the total under 1,300.

The quota is not Starter’s only limit: 5 concurrent executions and up to 5 minutes per execution. Levels and overage are detailed on the n8n pricing page, and the cost calculator redoes the math with your volumes, for n8n and for the other tools.

If you self-host the Community edition, these executions are not billed: the limit is your server. See n8n Cloud vs self-hosted.

What drives the counter up, and how to avoid it

• Too tight an interval on a Schedule Trigger. It is the leading cause of going over quota in our calculations. When a polling node or a webhook exists for your source, it counts only the runs that do something.
• A webhook called for nothing. Every incoming request counts, even an empty one. A webhook whose address gets around can use up quota without producing anything.
• Splitting work into several separately triggered workflows. If one event starts three workflows, it counts three times. A parent workflow that calls sub-workflows counts once.
• Handling items one at a time. A daily digest (one trigger a day that processes the whole batch) uses 30 executions a month where one trigger per item uses hundreds.

What about n8n templates?

n8n publishes a library of workflow templates, designed by the vendor and by community members. According to the docs, you import a template into your instance, then fill in your credentials and adjust the configuration. n8n docs, “Use templates” (accessed November 11, 2026)

Before you activate one, read it the same way as above: look at its trigger. A template that starts with a Schedule Trigger set to one minute uses 43,200 executions a month, whatever it does next.

To see how n8n compares with a tool billed per step, read n8n vs Make; for everything else, the n8n profile and the n8n alternatives.