n8n Made Crystal Clear · chapter 3: Your First Workflow, Properly
Test run versus production run: what fires, what counts toward the quota, and what you...
2026-09-16
Below: the paragraph from the book that builds this idea, then the diagram itself (Figure 3.2), and a recap. About a minute of reading.
That single sentence has three consequences worth memorising before you publish anything. A Schedule Trigger counts "one execution every time the node fires, regardless of outcome", so a workflow that fires hourly and finds nothing to do still bills 720 times a month. A polling node is kinder: it counts "one execution only when new data is found", and polls that return no results do not count. Manual runs, sub-workflow runs and error-workflow runs do not count at all. Figure 3.2 lines the two modes up side by side.
Recap
- The idea: Test run versus production run: what fires, what counts toward the quota, and what you get to see.
- The picture: Figure 3.2, from chapter 3 ("Your First Workflow, Properly") of n8n Made Crystal Clear.
- Go deeper: the chapter builds this step by step, with recipes and sources at the end.
This diagram is one of many in n8n Made Crystal Clear.
Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.
Get the book
