Comment to DM API for lead magnets, creators, and campaign replies
Keyword-triggered private replies from Instagram and Facebook comments, inside Meta's messaging rules rather than around them. Now in beta on the Pro and Business plans.
Comment to DM API for teams using keyword-triggered private replies from Instagram and Facebook comments in compliant DM-style follow-up workflows.
Last updated: September 2026
Request beta access
Request comment to DM API beta access if your product needs keyword-triggered private replies, lead magnet delivery, or campaign-specific comment automation. It is included on the Pro and Business plans.
Comment-to-DM workflows need moderation context before private follow-up
What bundle.social handles
For teams turning public comments into private intent
The beta is especially relevant for creator tools, lead magnet products, social commerce teams, giveaway workflows, and agencies that need safer comment-triggered follow-up.
Workflow
How it works
The comment-to-DM flow starts at the post level, checks comment intent and eligibility, then records every public and private action taken.
Select eligible campaign posts
Choose which Instagram or Facebook posts listen for comment keywords instead of applying one global rule everywhere.
Match the comment intent
Capture the keyword, comment, author, media, account, and campaign context that explains why the private path should start.
Send and record the follow-up
Send the private reply or DM and store the result so teams can see sent, skipped, failed, or retried runs.
Implementation
How to get the comment to DM API beta
The comment to DM API is in beta. It runs on the public API and in the dashboard, and we enable it for each organization while the beta runs.
Pick a paid plan
DMs and automations are included on the Pro and Business plans, with monthly limits per connected account.
Request beta access
Send the form on this page or message us from the dashboard. We turn the beta on for your organization.
Opt in each account
Messaging is enabled per connected account. Accounts connected before the beta may need to reconnect to grant messaging permissions.
Capabilities
What the comment-to-DM beta covers
This page focuses on campaign-specific keyword workflows and private follow-up rather than broad social auto-reply automation.
Post-level keyword rules
Flows decide which posts, keywords, and accounts can trigger private follow-up, instead of one global rule everywhere.
Public-plus-private coordination
One flow can post a public acknowledgement, send a private reply, and continue in DMs where the provider supports that path.
Duplicate and error control
Each run has an idempotency key, skipped-state tracking, provider response detail, and an audit record for the original comment.
Platform specifics
Comment to DM needs campaign and moderation context
The useful workflow is not just sending a private message. It is matching the right comment, avoiding duplicate sends, and preserving why the automation ran.
Post-level configuration
Teams decide which posts can trigger private replies instead of applying one global rule everywhere.
Keyword intent
The matched phrase travels with the run so support and growth teams know why a person entered the flow.
Auditability
Every public reply, private reply, skipped run, or provider error has a clear status.
Supported surfaces
Beta limitations
- Comment-triggered private replies depend on provider support, Meta permissions, account eligibility, and supported comment surfaces.
- Meta allows one private reply per comment, so a flow cannot send a second private message from the same comment.
- This workflow is not a generic outbound DM blasting workflow.
- Teams still need moderation and escalation paths when comments are sensitive, abusive, or ambiguous.
- Beta access is included on the Pro and Business plans and turned on per organization. The Free plan does not include DMs or automations.
- During the beta, conversations, messages, and automation run history are kept for 30 days.
- Official platform rules still apply, including permissions, messaging windows, review requirements, and provider payload limits.
FAQ
Questions developers ask before building
Is comment to DM API available in bundle.social today?
Yes, in beta. It is included on the Pro and Business plans, over the public API and in the dashboard. We turn the beta on for each organization by hand, so request access with the form on this page or message us from the dashboard.
Which plans include DMs and automations?
Pro includes 200 sent DMs and 200 automation runs per connected account each month, Business includes 1,000 and 1,000, and Enterprise limits are set per contract. Incoming messages do not count. The Free plan does not include DMs or automations.
What does beta mean for my integration?
Endpoints, payload shapes, limits, and supported surfaces can still change while the beta runs. During the beta, conversations, messages, and automation run history are kept for 30 days.
Do Meta messaging windows and permissions still apply?
Yes. Meta permissions, account eligibility, messaging windows, payload limits, and review requirements still apply. bundle.social is designed to make those workflows easier to manage, not bypass platform rules.
Is comment to DM the same as auto reply?
No. Auto reply can include public comments, message replies, or payload replies. Comment to DM is narrower: a public comment becomes the trigger for a private follow-up where supported.
Does comment to DM work on TikTok?
No. TikTok automations in the beta can reply to comments publicly, but TikTok DMs are not supported, so there is no private follow-up on TikTok.
Next pages