Make
Visual automation platform to link apps and APIs in scenarios.
For a handful of scenarios you master, one script per flow with a detailed run log is simpler than Make, and easier to debug. The value of Make is elsewhere: its visual editor, its maintained app modules, its error recovery, and the fact that a non-technical colleague can edit it. If you are alone and comfortable with code, replaceable. Otherwise, self-hosted n8n is the right middle ground.
What you lose
- The visual scenario editor.
- App modules kept up to date.
- Scheduling handled for you.
- Turnkey operation history and error handling.
- Team permission management.
Existing alternatives to Make
- Activepieces Community EditionOpen source
Visual workflow builder with hundreds of connectors, installable with a single Docker command.
The most complete substitute, free to self-host under the Sustainable Use licence (source available, not a free licence).
The prompt to build it yourself
Build me a code-oriented scenario runner to replace Make, for the handful of scenarios I use. Stack: a Node project, SQLite (better-sqlite3), Express, node-cron. To do: - A scenario is a file in scenarios/ that exports a trigger (cron expression or webhook route) and an ordered list of steps. Each step is an async function that receives the output of the previous one. - The runner chains the steps, retries a failed step 3 times with increasing delay, then stops and records the step name and the error. - Each run is logged in SQLite: scenario, start and end, JSON input and output of each step, status. This history is my debugging tool, take care over it. - A minimal dashboard on localhost:4880: list of scenarios with the status of the last run; a click shows each step's data. - Webhooks arrive on the same Express app, with signature verification. Keys are in .env. - Two example scenarios: Stripe payment webhook to a Google Sheets row and a Telegram message; an RSS article summarised by an LLM then sent by email. - Localhost only, a single user, no telemetry. Out of scope: visual editor, module catalogue. README: adding a scenario, .env keys, and state that self-hosted n8n is the fallback if maintenance becomes painful.
Frequently asked questions
- Can Make be replaced by a custom-built tool?
- casevibecode verdict: Partly replaceable. For a handful of scenarios you master, one script per flow with a detailed run log is simpler than Make, and easier to debug. The value of Make is elsewhere: its visual editor, its maintained app modules, its error recovery, and the fact that a non-technical colleague can edit it. If you are alone and comfortable with code, replaceable. Otherwise, self-hosted n8n is the right middle ground.
- What is Make used for?
- Visual automation platform to link apps and APIs in scenarios.
- What alternatives to Make already exist?
- Activepieces Community Edition (open source), n8n Community Edition (free). Options to compare before committing to a custom build.
Community feedback
Readers tell what they built instead of this tool, or what broke along the way. Every entry is reviewed before publication.
No feedback published yet. Have you tried replacing this tool? Tell us about it.