Workflow automation free tools that hold up in production

Free means four different things

Most workflow automation free tools are free in one of four ways, and the difference decides whether you're still running the thing a year from now. Free as a capped tier on a commercial product. Free as open source you host yourself. Free as beta, which means free until the pricing page shows up. And free as a feature buried in software you already pay for, that nobody on your team has switched on.

We're two people at Stride AI. We build the systems we sell, so we also maintain them, which means all four kinds of free have at some point turned into either a bill or a Saturday afternoon for us. What follows is the list we'd hand to an operator who wants to stop paying a person to copy data between two apps, plus the honest note on where each one stops being worth it.

Write down the job before you open a tool

Every workflow automation tools list you find online ranks by integration count. That number is close to useless for you, because you're not buying a catalogue. You're buying one job getting done without a human in the loop.

Write the job as one sentence with a trigger, a rule and a result. "When a proposal comes back signed, create the project record, make the client folder, and post the name in the sales channel." Now you can tell which tool fits, because the sentence also tells you how often it fires, and frequency is exactly what free tiers meter.

We do this on paper before touching anything. It kills a lot of ideas at the first line, usually because the trigger doesn't exist: nobody marks the deal as won anywhere a machine can read. Fixing that is free, and it's the real work. The automation on top is the easy part.

The workflow automation free tools we'd install first

These are the connector-style tools, the ones where you click boxes together. They're where most businesses should start, because the first automation you build should take an afternoon.

Zapier

Zapier is the one most people mean when they say automation, and it earns that through sheer catalogue size. If your stack is ten SaaS products with public APIs, Zapier already speaks to all of them, and you'll get a working two-step flow before lunch.

The free plan is best understood as a proving ground. It's enough to confirm that the trigger fires and the record lands where you wanted, and it is not enough to run a business on. Once your flow starts firing on every new lead rather than every new client, you're on a paid tier, and Zapier bills by task, so a workflow that loops over a spreadsheet gets expensive quickly. Build the proof there, then decide whether to keep it or move it.

Make

Make gives you a visual canvas instead of a linear list, which matters the moment your workflow has branches. Iterators, error handlers and routers are in the builder rather than bolted on, so a flow with three possible outcomes stays readable.

The pricing model counts every module run, not every workflow run. A scenario that loops over 200 rows and touches three modules per row is 600 operations, and that arithmetic is what quietly eats a free tier. Sketch the loop before you build it.

n8n

n8n is one of the workflow automation tools Zapier now competes with directly, and it's the first on this list that you can genuinely keep. It's source-available under a licence that lets you self-host for nothing and stops other people reselling it as a service. Run it on a small VPS and the task limit is your CPU.

There's a code node, so when the visual builder runs out of road you write ten lines of JavaScript instead of building a workaround out of four extra steps. That single escape hatch is why we reach for it. The trade is that you now own a service: updates, backups, and a webhook URL that has to stay reachable. If nobody in your business can restart a container, this isn't free, it's deferred.

Activepieces

Open source, self-hostable, and deliberately shaped like Zapier so the mental model transfers. The connector library is smaller, which is the whole story: check that your three critical apps are supported before you invest a day, because writing your own piece is a real project rather than an afternoon.

It's a good fit when you want the visual builder in your own infrastructure and n8n feels heavier than the job deserves.

Workflow automation developer tools worth the extra setup

If you or someone in the business can read code, the picture changes. The best workflow automation tools free of any licence fee are the ones you host yourself, and most of them assume a developer. There's a good argument doing the rounds, made at exe.dev and picked up by Simon Willison, that developer tools in particular should be open source, and the reasoning applies neatly here: the tool that runs your business logic is a bad place to be locked in.

GitHub Actions

Most teams already have this and don't use it for anything except tests. Actions has a schedule: trigger, which means it's a cron server with logs, secrets management and a UI that your team already knows how to read. Public repositories run free, and private ones come with a monthly allowance that a handful of nightly jobs won't dent.

We use it for the boring recurring work: pulling a report, reformatting it, pushing it somewhere. Anything that runs on a timer and finishes in under a few minutes belongs here before it belongs in a paid automation platform.

cron and systemd timers

The least fashionable entry and the one we'd still bet on in ten years. A shell script plus a cron line does the job for a large share of scheduled workflows, costs nothing, and has no vendor. The failure mode is silence: cron will not tell you it stopped working. Add one line that pings a monitoring endpoint on success, and you've closed the only real gap.

Windmill

Windmill turns scripts into workflows, and it's the right answer when your logic is already code but you want schedules, retries, a run history and a small UI on top. Open source, self-hostable, and it treats Python and TypeScript as first-class rather than as an escape hatch. If your automation is mostly "run this script when that happens, and tell me when it breaks", this is a shorter path than rebuilding the script inside a visual editor.

Node-RED

Flow-based, open source, running on Node.js, and dominant in anything touching hardware or MQTT. If your workflow involves a sensor, a machine on a factory floor, or a device that speaks a protocol no SaaS connector has heard of, Node-RED is the tool with the community that solved it already.

Playwright and Kitesurf

Some workflows have no API at their most important step. A supplier portal, a government form, an old internal system: the data is only reachable through a browser. Playwright is free, open source, and drives a real browser well enough to log in, click through, and pull the file down.

For the agent version of that job, Cloudflare launched Kitesurf in August 2026, a cloud-hosted browser built for AI agents rather than people. It drops the parts agents don't need, themes and tabs and extensions, and focuses on context windows, token cost and scale. Cloudflare says it decided to build it 12 weeks before launch, that it runs on top of Workers, and that it uses less CPU and memory than Chromium for common agent tasks like screenshots and HTML extraction. It passes around 215,000 web platform tests so far. It's free while in beta inside Browser Run, which puts it firmly in category three above: free until it isn't. Worth prototyping with, not worth building your invoicing on yet.

The llm command line tool

Simon Willison's llm is a command line tool for talking to models, open source, with plugins for most providers and logging that keeps every prompt and response in a local SQLite file. The August 2026 release added reasoning traces, OpenAI Responses support and server-side tools. In a workflow, it's the piece that does the judgement step: classify this email, extract these five fields, summarise this thread. You pipe text in, you get text out, and it composes with cron and shell scripts the way everything on this half of the list should.

The AI step is where free stops

Most interesting automations now have one step in the middle that requires reading something and deciding. That step is where your costs live, and where the free tiers get careful.

On the consumer side there's more free capacity than there was. OpenAI expanded access to GPT-5.6 Luna for free ChatGPT users with unlimited everyday chats, and improved GPT-5.6 Sol alongside it. That's useful for a human sitting at a keyboard and not useful for a workflow, because a workflow needs an API key and API keys bill per token.

The pricing under those keys has edges that will surprise you. Developers noticed that Codex ships a model catalogue listing gpt-5.6 with a 272,000 token context window while the published spec for the model is 1,050,000, and 272,000 is also the point where the API reprices: past that many input tokens, the whole request bills at 2x input and 1.5x output, including the tokens under the line. OpenAI's stated reason for the cap is cache-read cost. The practical lesson for your workflow is the same either way: a step that stuffs an entire document history into every call can cross a threshold and double its own bill without changing behaviour. Keep the context you send small and deliberate.

There's a safety edge too, if you're letting a model run commands rather than just write text. From 14 August 2026, Anthropic makes Auto Mode the default in Claude Code for Pro, Max and Team plans. Their reasoning is worth sitting with: in their tests, the classifier caught 89 percent of dangerous commands while human reviewers caught 13.6 percent. People approving prompts all day stop reading them. If your automation asks a person to click approve on every run, assume within a month that person is clicking without looking, and design the guardrail into the workflow instead.

What a stack under 30 dollars a month looks like

Someone posting on r/artificial in August 2026 described their setup: a scraper found on GitHub, a cheap Claude subscription, a no-code database, and Zapier holding it together. Under 30 dollars a month, run by one person between shifts at a cafe, and their words for it were that they were scared it actually worked.

That shape is right, and the fear is right too. Here are workflow automation tools examples in the same spirit, sized for a small business:

• Scheduled data pull: GitHub Actions on a cron schedule, a Python script, results written to a database. Cost: nothing.
• Inbox triage: llm on the command line classifying incoming messages into three buckets, with anything ambiguous going to a person. Cost: cents per day in tokens.
• Client onboarding: n8n on a small VPS, triggered by a webhook, creating records across four systems. Cost: the VPS, around the price of two coffees.
• Portal scraping: Playwright in a scheduled job, pulling the file that has no API. Cost: nothing beyond compute.

The total sits in the same range as that Reddit stack, and the honest risk is identical: every one of those pieces was assembled by one person, and if that person leaves, nobody knows why the Tuesday job exists.

Where each of these breaks

Keeping your workflow automation tools free means someone in your business does the maintenance instead of a vendor. Self-hosted n8n needs updating. A cron job needs a heartbeat. A scraper breaks when the supplier redesigns their portal, and it breaks silently, which is worse than breaking loudly.

So the real question to ask before you build is who owns it on the day it fails. If the answer is nobody, buy the paid tier and let the vendor own the uptime. If the answer is a named person with the access to fix it, self-host and keep the money.

The second thing that breaks is the undocumented workflow. Every automation should have a one-line comment saying what it does and who asked for it. We've inherited enough systems without that line to consider it non-negotiable, and it costs 30 seconds.

What we'd skip

We'd skip building an agent that decides which workflow to run before you have workflows that run reliably on a schedule. The deterministic version is cheaper, easier to debug, and correct more often.

We'd skip any tool whose free tier requires your data to sit in their cloud, if that data includes client information you've promised to keep in the EU. Check where the servers are before you check the feature list.

We'd skip paying for a platform to do something your existing tools already do. Your CRM probably has automations built in. Your project tool has rules. Those are free in the fourth sense, they're already covered by what you pay, and they're the first place to look.

If you want a second pair of eyes on which of your processes are worth automating and which ones just need someone to write the step down, that's what our AI services are for. We'll tell you when the answer is a cron job and a shell script, because often it is.