n8n, Zapier, Make, or a file of Python

What the visual tools give you

It is fashionable among engineers to sneer at Zapier. Do not. What these tools sell is not drag-and-drop; it is several hundred integrations where somebody else has already solved OAuth.

Getting a new row in Google Sheets into a Slack channel takes about four minutes in Make. Writing it yourself means registering an app, implementing an OAuth flow, storing and refreshing tokens, handling revocation, and reading two API references. That is a day, and it is a day of work that produces nothing anybody wanted.

If the automation is mostly moving data between services other people run, the visual tool is not the amateur choice. It is the correct one.

Read the meter before you design the flow

The pricing model shapes the design, so learn it first.

• Zapier charges per task, where a task is roughly one step doing one thing.
• Make charges per operation, with a similar meaning.

A twelve-step flow run a thousand times a month is twelve thousand billable units, not one thousand. And a loop over fifty rows is fifty operations per run, not one. Teams routinely design an elegant flow and then discover it costs more than the salary of the person it saved.

This is not a trap so much as a fact to design around: fewer, fatter steps, and push loops into a single call to something you wrote.

Where they hit a wall, and why

Four walls, each with a mechanism rather than a vibe:

• Loops with conditions. Every serious tool has iteration now, but early exit, nested conditions and accumulating state are painful, because a canvas has no variables in the way a language does. You end up building a program in a diagram.
• Version control. The flow is stored as a JSON blob. You can export it to git; you cannot meaningfully review the diff, because node ids and coordinates churn on every save. So code review and rollback (the two things that make a change safe) do not really work.
• Testing. There is no unit test. You test by running it, usually against live data, usually in production.
• Local development. Some platforms have it, most do not, so “try something” and “change the live system” become the same action.

The hybrid that usually wins

Use the visual tool as trigger and glue, and put the part with real logic behind a single HTTP call to a function you wrote.

The tool handles the Gmail connection, the Slack post and the schedule. Your function receives a JSON payload and does the branching, the retries, the validation and the model call. The connectors stay free; the logic lives in git where it can be reviewed, tested and rolled back.

This is the shape most durable small automations end up in, and almost nobody starts there.

The free path

Every paid tool above has a free equivalent you can run yourself:

• n8n, self-hosted with one Docker command, for the same visual model.
• Node-RED, older, extremely stable, strong for event and device work.
• Windmill, if what you want is scripts with a UI over them.
• Apache Airflow or Dagster, if what you actually have is a scheduled data pipeline with dependencies.
• cron plus a Python file, which remains undefeated for a single job.

Learn the names of the paid ones because job adverts name them. Run the free ones because a small server costs less per month than one Zapier plan.

Three questions to decide

1. Does it need a loop with a condition and an early exit?
2. Does anybody need to review a change before it goes live?
3. Does it touch money, or send messages to customers?

One yes: either shape works. Two or more: write code.