Can I vibecode ManyChat?

NOT REALLY · don't bother

price $39/moyou'd save $468/yrbuild time a weekendcategory 🐦 social mediareplaced by 0 people

The flow builder is the visible part and it is not the hard part: keyword triggers, branching, delays and tags are a weekend of CRUD and a state machine. The hard part is that every message goes through Meta, and Meta decides who gets to send it. To reply to arbitrary strangers who DM your Instagram account you need a reviewed app with advanced messaging permissions, a linked Facebook page, business verification, and compliance with the 24 hour window and human agent tag rules. ManyChat has already cleared all of that and maintains it as the APIs churn. A DIY bot works fine for accounts you personally control in dev mode, which is exactly the audience that does not need automation.

the prompt

Build a self-hosted Instagram/Messenger DM autoresponder called "dmflow". Node 20, TypeScript, Fastify, better-sqlite3, no ORM, no frontend framework.

Stack decisions are final, do not offer alternatives.

What it does:
1. POST /webhook receives Meta Messenger and Instagram messaging webhook events. GET /webhook handles the hub.challenge verification using VERIFY_TOKEN from .env.
2. Verify the X-Hub-Signature-256 header against APP_SECRET and reject anything that fails.
3. Store contacts (platform, psid, first_seen, last_inbound_at, tags) and a messages log in SQLite at ./data/dmflow.db. Create the schema on boot if missing.
4. Load flows from ./flows/*.json. A flow has: id, triggers (array of keyword strings, matched case-insensitively on the inbound text, plus an optional "default" fallback flow), and steps. Step types: send_text, send_buttons (title plus up to 3 postback buttons), wait (seconds), add_tag, set_field, goto (another flow id).
5. Run a small state machine per contact: current flow id, current step index, collected fields. Persist state so a restart resumes correctly.
6. Outbound sends go to the Graph API /me/messages with PAGE_ACCESS_TOKEN. Respect the 24 hour window: if last_inbound_at is older than 24 hours, refuse to send and log the reason instead of retrying forever.
7. Retry failed sends up to 3 times with exponential backoff, then dead-letter the message into a table.
8. Serve a single read-only HTML page at / rendering contacts, their tags, and the last 50 messages. Plain server-rendered HTML, no JS build step.

Out of scope: WhatsApp, SMS, email, a visual flow editor, multi-user auth, analytics dashboards, broadcast sending.

Secrets in .env only: VERIFY_TOKEN, APP_SECRET, PAGE_ACCESS_TOKEN, PORT. Ship .env.example. No telemetry, no third party services beyond Meta's Graph API.

Include two example flows in ./flows: a keyword flow for "price" and a default greeting flow.

Write a README that states plainly that until the Meta app passes review for advanced messaging permissions, this will only reply to accounts added as app testers, and that this is a limitation of Meta, not of the code.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

Because the bottleneck is access, not code. Anyone selling through Instagram DMs needs messages that actually reach strangers who commented on a post, and that requires permissions Meta grants to reviewed apps and revokes when policy shifts. ManyChat absorbs that risk, keeps the connectors alive across API versions, and hands a marketing person a canvas they can edit at 11pm without a deploy. Fifteen dollars a month against a broken funnel is not a hard call.

what you lose

xPre-approved Meta Business Partner status, so your bot only talks to testers until review passes

xThe visual flow editor that non-engineers can actually edit without touching JSON

xMulti-channel parity: WhatsApp, SMS and email in one contact record

xComment-to-DM triggers, story reply triggers, ads-click entry points and other Meta surface coverage

xDeliverability guardrails: 24 hour window handling, message tags, broadcast policy compliance baked in

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced ManyChat ($39/mo) with one prompt"