What is low-code workflow automation? (And where the code shows up)
Low-code workflow automation means building an automation mostly out of ready-made steps, then typing a short custom rule into the one step the menu cannot handle. The name describes who is allowed to build, not how much code is involved. That one typed step is where every tradeoff lives.
What "low-code" actually describes
Low-code workflow automation means you assemble most of an automation from ready-made steps, then type a short piece of custom logic into the one or two steps nothing on the menu covers. The menu handles the ordinary parts: an email lands, a form gets filled in, a row is added to a spreadsheet, a message posts to Slack. The typed part handles the rule that is specific to your business, like deciding which of four managers signs off on a refund over $500.
Where the typed part shows up
Always in the step you care most about, and always with limits attached. Vendors call it a code step, a script step, a formula field or an expression. On Zapier, a code step gets 1 second to finish on the free plan, 30 seconds on Pro and Team, and 2 minutes on Enterprise, each capped at 512 MB of memory. Microsoft prices the Power Automate Premium plan that turns on its non-standard connectors at $15 per user per month, billed yearly. So the step that needs custom logic is usually the step that moves you onto a paid tier.
The cost that arrives later
Money is the smaller half. Whoever typed the expression now owns that automation. Engineers on Hacker News describe the same result over and over: the little script has no version history, nobody else can read it, and when its author leaves the flow becomes untouchable. If every step you need is already on the menu, stay there and skip this category entirely. If it is not, treat the first formula you type as a decision worth recording, not a detail.
Last updated: Aug 28, 2026