[verdict][generated prompt][source: make.com]
Can I vibecode Make?
// buildable in a weekend, but real gaps stay open
A handful of workflows can be coded quickly, but Make's paid value is the visual builder, app modules, scheduling, observability, and maintenance.
confidence: high
what it is: Visual automation platform for scenarios across apps and APIs
Buildability index · an editorial game
- Price 12 $/month weight: plus 2
- Time weekend weight: plus 2
- Category automation no weight
- Moat integrations · execution quality weight: minus 2
- Confidence high weight: plus 1
- What you lose 6 items weight: minus 3
- Site make.com (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Implement the needed scenarios as scripts or n8n workflows with API calls, retries, and logs.
what you need
- API keys/OAuth
- hosted scheduler/worker
- secrets
- logs
- retry handling
Good smaller Zapier comparison; same reasoning but different builder style.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a code-first workflow runner to replace Make for my handful of scenarios. Requirements:
- A Node project where each scenario is one file in scenarios/ exporting a trigger
(cron string or webhook route) and an ordered list of steps, each step an async
function that receives the previous step's output.
- The runner executes steps in order, retries a failed step 3 times with
exponential backoff, then halts the run recording the step name and error.
- Every run saved to SQLite (better-sqlite3): scenario, start/end, per-step input
and output JSON, status. That history is the debugging story, make it good.
- A minimal dashboard on localhost:4880 (Express, server-rendered): scenario list
with last-run status, click into a run to see each step's payload.
- Webhook triggers land on the same Express app with signature verification
helpers; cron triggers via node-cron. All credentials in .env.
- Ship two example scenarios: a Stripe payment webhook appends to a Google Sheet
and sends a Telegram message; an RSS post gets an LLM summary drafted as email.
- Binds to localhost only, single user, no accounts, no telemetry.
- Out of scope: a visual drag-and-drop builder and an app-module catalog. Scenarios
are code, that is the point of this build.
- README: how to add a scenario, .env keys, and a note that self-hosted n8n is the
off-the-shelf fallback if maintaining this stops being fun. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- visual scenario builder
- app modules
- scheduling
- operations history
- error handling
- team governance
Why people still pay
They pay because workflows evolve and break; a maintained builder reduces the upkeep.
moat: Integrations Execution quality what a moat is
integrations/workflow engine
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Activepieces (opens in a new tab) — Open-source automation platform with app pieces, triggers, and actions. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.