IG AUTOMATION · LIVE ON A REAL ACCOUNT · PROJECT 11
Instagram Comment Engine
Comment a keyword, get a reply in seconds — running on a real 8.6k-follower account
The problem
Creators pay $15–99/month for tools like ManyChat to auto-reply when someone comments a keyword — and those tools cap DMs, brand your replies, and own your data. Under the hood it's a webhook and one API call.
What I built
The same engine, self-owned and free to run: when anyone comments “book” on @humancheatcodes_, Meta fires a webhook to a Cloudflare Worker that replies to the comment within seconds, 24/7 — plus a live control-room dashboard (inside my Nexus AI OS product) to monitor and drive all of it: totals, per-post performance, activity feed, keyword & reply editing, one-click pause.
How it works
- A Meta app subscribed to Instagram comment webhooks pushes every new comment to a Cloudflare Worker — no polling, no server, replies land in seconds.
- Replies rotate through multiple phrasings and skip the account's own comments, so the pattern doesn't trip Instagram's spam filters.
- A backlog engine found 180+ older keyword comments and drains them on a cron — 8 replies every 5 minutes — after a burst test proved Instagram rate-limits anything faster.
- State lives in Workers KV: config (keywords, reply variants, on/off), rolling stats by day, and a 300-entry activity log — all exposed through a token-protected JSON API with CORS.
- The dashboard is a module in Nexus AI OS (Next.js 16): stat cards, a 14-day reply chart, per-reel match/replied/pending counts scanned live from the Graph API, and config that writes straight back to the Worker.
Stack
Cloudflare Workers + KV + Cron TriggersMeta Graph API (Instagram Login, webhooks)Next.js 16 dashboard (Nexus AI OS)Zero monthly cost
What it proves
Real third-party API integration end to end — OAuth-style app review flows, webhook verification, rate-limit engineering, serverless state, and a product-grade control panel on top.
Honest limitations
WHAT THIS DOESN'T DOReplies only — DMs go through Meta's app-review gate and a separate tool handles them for now. Username capture on older comments is limited by what the Graph API returns. It runs one account today; multi-account is architecture, not a rewrite.
Want something like this built?
Design, code, launch and growth — handled start to finish.
Book a free call