Key takeaways
- Open-source comment-to-DM is real but rarely free, because you still supply a Meta app, hosting, token refreshes and your own monitoring.
- Password-based GitHub scripts are the only truly zero-cost option, and they are the ones that get accounts restricted.
- Budget one to two days for a self-hosted n8n build and two to five days for an API starter kit, plus monthly upkeep for tokens and platform changes.
- Standard Access covers accounts you own or manage, while agencies serving client inboxes need Advanced Access with App Review and Business Verification.
In this article
- What counts as open-source comment-to-DM, and how to judge each option
- 1. Self-hosted workflow tools such as n8n
- 2. An open-source starter kit on the official Instagram API
- 3. GitHub scripts that log in with your Instagram password
- 4. Meta Business Suite's built-in comment to message
- 5. The free tier of a hosted tool
- The real cost of each option, in hours
- The verdict on open-source comment-to-DM
Every few weeks someone on r/InstagramMarketing asks whether a free or open-source alternative to ManyChat's comment-to-DM exists, and the replies split into two camps that are both half right. Yes, you can build an open-source comment-to-DM system. No, it is not a download and a login. A private reply to a comment is a call to Meta's messaging API, so whatever you run has to carry a Meta app, a permission set, a public HTTPS endpoint, a token that expires every 60 days, and a server that is awake at 2am when a reel takes off. The code is the cheap part. What follows sorts the free options into five categories, says which ones actually deliver a DM, and puts hours against each so you can compare them with a subscription instead of comparing them with zero.
Short answer: open-source comment-to-DM is real but rarely free. Self-hosted workflow tools and API starter kits can send private replies, yet you still supply a Meta app, hosting, token refreshes and your own monitoring. Password-based GitHub scripts are the only truly zero-cost option, and they are the ones that get accounts restricted.
What counts as open-source comment-to-DM, and how to judge each option
An option only belongs in this comparison if it can send a private reply to a comment through Meta's official API. Everything else is a public comment reply with extra steps.
Four questions separate the categories, and they are the ones to ask before you clone anything:
- 1Does it send a DM at all? Meta allows one private reply per comment, within 7 days of that comment being created, documented on the private replies reference. A tool that cannot make that call is not a comment-to-DM tool.
- 2Who owns the Meta app? Self-hosted means you register the app, pick the login path and hold the tokens.
- 3Where does it run, and who gets paged? Webhooks arrive whether or not your box is up, and a missed delivery is a lead that never knew you replied.
- 4How does it authenticate? Official API, or your password. That one answer decides whether the project is a weekend build or an account risk.
Score each category on those four and the picture gets clear quickly.
1. Self-hosted workflow tools such as n8n
This is the most capable free route, and the one most people underestimate. n8n's Community Edition is free to self-host, and its built-in Facebook Trigger node subscribes to Instagram messages and comments events, so receiving a comment is native rather than a hack. The n8n documentation covers the node setup, and our deeper write-up on Instagram DM automation with n8n, Make and Zapier walks the build.
What the licence does not cover is the Meta side. You create the app, request the messaging permissions, handle the webhook verification handshake, and store state somewhere that survives a restart. Then you own the conversation logic forever, because every policy change and every phrasing you did not anticipate becomes another branch you maintain by hand. A realistic first build for someone comfortable with APIs is a weekend, and realistic upkeep is an hour or two a month plus the occasional bad evening. Worth it when you already self-host n8n for other work. Expensive when this would be the only workflow on the server.
If the plumbing is the part you want to skip rather than own, HyperDM's comment-to-DM feature is the same mechanism with the Meta app, the retries and the 7-day window already handled.
2. An open-source starter kit on the official Instagram API
Public repositories that wrap Meta's messaging endpoints into something deployable are a head start on code you will still read line by line, because the permission model is where self-hosted Instagram automation gets expensive.
Meta's access tiers decide the scale of the job. Standard Access covers automating accounts you own or manage, which is most solo operators and single-brand businesses. Advanced Access, which requires Instagram API App Review and Business Verification, is the level you need once your app serves accounts you do not own, so an agency running client inboxes is in the review queue whether it wanted to be or not. The token chain is the other recurring cost: an authorization code valid for one hour, exchanged for a short-lived token valid for one hour, exchanged for a long-lived token valid for 60 days that must be refreshed before it expires. A refresh that fails quietly looks exactly like a slow sales week, right up until someone opens the inbox and finds a fortnight of unanswered DMs. Our guide to building your own Instagram DM bot has the full sequence.
3. GitHub scripts that log in with your Instagram password
These come up first in a search and should come up last in your shortlist. A script that asks for your Instagram username and password acts as you, through the app's private endpoints, which is the exact pattern Meta's systems read as inauthentic automated activity. Instagram's Terms of Use prohibit automated activity run through a login, and the consequence shows up as the automated behaviour warning, a messaging restriction, or a login you cannot complete.
The practical failure mode is just as bad. Private endpoints change without notice, the project breaks, and a maintained fork fixes it two weeks later. None of this is a licence problem. The code genuinely is free. The risk is that you are trading a $17 subscription against the account that holds your audience. We covered the mechanics in what the Instagram automated behavior warning means. If a repository's setup instructions include your password, close the tab.
4. Meta Business Suite's built-in comment to message
Not open source, genuinely free, and routinely forgotten. Meta Business Suite includes Inbox automations with a "Comment to message" rule that sends a message reply to comments containing keywords you set, documented in Meta's own help centre. No server, no tokens, no deployment.
The ceiling arrives fast. You get keyword matching and a fixed reply. No branching, no follow-up sequence, no link tracking, no analytics view telling you which post earned the conversation. There is no dedupe logic you control and no way to hold a send during a spike. As a first test of whether your audience will comment a keyword at all, it is the cheapest experiment available, and plenty of businesses never need more than it.
5. The free tier of a hosted tool
Worth naming because the comparison usually gets framed as open source against a paid subscription, when the real question is free against free. A hosted free tier hands you the Meta app, the review status, the webhook retries and someone else's on-call rotation, and charges nothing until volume arrives.
The trade is ceilings and branding. ManyChat's Free plan, as of November 2026, includes 25 active contacts, up to 4 live triggers, 2 channels and ManyChat branding, read from manychat.com/pricing. HyperDM's Free plan includes 50 conversations a month with the AI agent on every conversation. Both are capped on purpose, and a viral post exhausts either. Read a free tier as a trial with no deadline rather than a permanent home. If you are shopping that way, our round-up of free ManyChat alternatives for Instagram covers what each $0 plan actually includes, and a free ManyChat alternative that covers your volume beats a self-hosted build nobody maintains.
The real cost of each option, in hours
Licence cost is the number everyone compares. Setup hours and upkeep are the numbers that decide it.
| Option | Licence cost | You must supply | Setup | Monthly upkeep | Sends a real private reply |
|---|---|---|---|---|---|
| Self-hosted n8n | $0 (Community Edition) | Meta app, server, state storage | 1-2 days | 1-2 hours | Yes |
| Open-source API starter kit | $0 | Meta app, hosting, token refresh, review if agency | 2-5 days | 2-4 hours | Yes |
| Password-based GitHub script | $0 | Your account's safety | Hours | Constant breakage | Yes, at real risk |
| Meta Business Suite automation | $0 | Nothing | 10 minutes | None | Yes, keyword only |
| Hosted free tier | $0 to a cap | Nothing | 10-20 minutes | None | Yes |
Two things stand out in that table. The genuinely free builds cost days, and the genuinely instant options cost ceilings. Nothing here is free in both senses.
The verdict on open-source comment-to-DM
Open-source comment-to-DM is worth the setup in two situations: you already run n8n or similar infrastructure for other work, or your logic is strange enough that no hosted product models it. In both cases you pay in hours rather than dollars, and the hours never stop. For everyone else, the honest comparison is a free tier or a low paid plan against a weekend of work plus permanent ownership of tokens, webhooks and uptime. Try Meta Business Suite's built-in rule first to prove your audience will comment a keyword at all, then decide. When you want the plumbing handled rather than owned, compare what each tier includes on HyperDM's pricing page.
Frequently asked questions
HyperDMRun the automations. Add AI when you’re ready.
Comment-to-DM, keyword replies and follow gates — set them up, test them, then add optional AI answers from your real catalog. Free on one DM channel, 50 conversations a month, no card.



