What is no-code automation? (And what a run costs)
No-code automation means setting up software to handle repeating work by clicking through a builder: an invoice arrives, a file gets filed, a Slack message goes out. The build is the cheap part. What catches people out is the meter, because every platform counts a run differently and the same job can cost wildly different amounts.
No-code automation is a build with two costs, and most first-timers only plan for one. You pick what starts the work (an invoice lands in the inbox, someone submits a form), then the steps that follow. That part takes an afternoon. The running cost and the upkeep are what actually decide whether the thing survives.
What a run costs
Each platform counts a different thing. Zapier charges a task for every action that finishes, so a flow that saves a file and then posts to Slack burns 2 tasks per run, and the free plan's 100 tasks a month is gone after 50 runs. Make renamed its billing unit from operations to credits in January 2026: an ordinary step is still 1 credit, and the free tier gives 1,000 a month, but Make's own AI steps now charge by how much they actually process, so reading a long document is no longer flat rate. n8n counts the whole run once, so a 20-step flow and a 2-step flow each cost 1 of the 2,500 runs on its 20 euro plan.
Where the "no" runs out
Three walls come up fast. Speed: on Zapier's free plan a flow that watches for new data only looks every 15 minutes, so nothing is instant until you pay for the 2 minute check. Coverage: if your app has no ready-made connection, you fill in the technical details by hand, which is where non-technical builders stall. Judgment: every branch has to be drawn before the first run, so work that depends on reading a messy email has no box to tick. Count real runs on a free tier for a week before picking a plan.
Last updated: Aug 14, 2026