Understand the meter
Usage Guides
Source-linked explanations of tasks, operations, executions, retries, and plan usage.
13Published guides3Platform routes1Verification standard
Published field notes
Start with the latest evidence.
01Usage Guides
Make Webhooks: Parallel Processing vs Process Data in OrderMake runs webhook-triggered scenarios in parallel by default. Here is how Process data in order changes queue behavior,…
Make
02Usage Guides
Do Zapier Search Steps Count as Tasks?Zapier search steps only use a task under one specific setting. Here is the documented rule, two worked…
Zapier
03Usage Guides
Do Zap Replays and Error Handlers Use Tasks?Errored steps never bill, but a successful retry does. This guide separates errored-step replay, full-run replay, and error-handler…
Zapier
04Usage Guides
How Looping by Zapier Uses TasksThe Looping step is task-free, but successful ordinary actions after it multiply by iteration. See worked models for…
Zapier
05Usage Guides
Do Zapier Filters, Paths and Formatter Steps Count as Tasks?Filter, Paths, and Formatter steps don't use Zapier tasks under current rules — but legacy plans need an…
Zapier
06Usage Guides
Do Routers and Filters Count as Operations in Make?Routers and filters are credit-free in Make, but they don't make a branch free. Here's the documented rule,…
Make
07Usage Guides
How Many Tasks Does a Multi-Step Zap Use?There's no single task cost for a multi-step Zap. This guide walks through the current counting rule, worked…
Zapier
08Usage Guides
Do Make Triggers Use Credits When They Find No Data?A scheduled Make trigger consumes one credit per check, even with zero results. See the 15-minute worked estimate,…
Make
09Usage Guides
How Aggregators Reduce Make Operations: A Worked GuideAdding an aggregator can cut Make operations from 11 to 3 in the documented example — but grouping,…
Make
10Usage Guides
Make Iterator Operations Explained With a Worked ExampleAn iterator spends one credit to split an array into bundles; the multiplication happens downstream. See the worked…
Make
Browse by intent
Choose the kind of answer you need.
Categories describe the job of the article. Platforms stay separate, so one guide can remain useful without duplicating content.
01
Find the failure pointDiagnostics
02
Symptoms, root causes, safe fixes, and a verification step.
10 published guidesUnderstand the meterUsage Guides
03
Tasks, operations, executions, bundles, retries, and plan rules.
13 published guidesChoose with evidenceComparisons
Billing models, workflow behavior, and implementation tradeoffs.
3 published guidesPlatform routes
Follow one platform without entering a content silo.
Platform labels cut across diagnostics, usage guides, comparisons, calculators, and tested workflows.