Can I vibecode Soccial AI?
price $139/moyou'd save $1668/yrbuild time multi-daycategory social-mediareplaced by 0 people
KINDA
MOATintegrationsscale infraexecution polish
AI Instagram DM and comment automation with a CRM that turns followers into customers you own
The Build Prompt
copy it and go buildready to paste · 1,604 chars
Build a self-hosted Instagram DM auto-responder for my own Instagram professional account, in this empty folder. Stack: Node 22 + Hono + better-sqlite3 + the Anthropic SDK (claude-sonnet-5). One small server, no frontend. Secrets in .env: IG_ACCESS_TOKEN, IG_ACCOUNT_ID, META_APP_SECRET, META_VERIFY_TOKEN, ANTHROPIC_API_KEY. Endpoints: - GET /webhook: Meta's hub.challenge verification handshake. - POST /webhook: verify X-Hub-Signature-256 with META_APP_SECRET, ACK 200 immediately, process async. On each incoming DM: skip echoes of my own outbound messages (is_echo); dedupe by message id in SQLite; load the last 10 messages of that conversation from SQLite as context; generate a reply with Claude using the editable system prompt in persona.md; send it via POST https://graph.instagram.com/v23.0/me/messages with recipient.id set to the sender's IGSID; log both sides to SQLite. Guardrails: never reply twice to the same message id; hard cap of one auto-reply per user per two minutes; if the model's reply contains the token HUMAN, send nothing and log it for me instead. Write a README that walks through the Meta side, which is the actual hard part: create a Meta app, add the Instagram API with Instagram Login, generate a long-lived access token for my account, subscribe the app to the messages webhook field, and expose this server with a Cloudflare Tunnel. Note plainly that in development mode this works only for my own account, and that is the point. Deliberately out of scope: comment automation, multiple accounts, any CRM, Shopify or calendar integrations, and Meta App Review.
What you lose
- ✕Anyone-but-you: without Meta App Review your app only serves accounts you add as testers
- ✕Shopify and GoHighLevel context behind replies, and the CRM around the conversations
- ✕Comment-to-DM automations, scheduled follow-ups, and human-approval gates on AI writes
- ✕Someone else babysitting webhook uptime, token refresh, and Meta API deprecations
Prior art / alternatives
Why it still works
The moat is Meta's gate, not the code: App Review + business verification to operate beyond your own account, plus permanent connector upkeep across four platform APIs.