Comment to DM API
Coming soon

Comment to DM API for lead magnets, creators, and campaign replies

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: May 2026

WaitlistComment triggersPrivate follow-up

Join the waitlist

Join the comment to DM API waitlist if your product needs keyword-triggered private replies, lead magnet delivery, or campaign-specific comment automation.

We will only use this email for bundle.social product updates and early access communication.

Comment-to-DM workflows need moderation context before private follow-up

A simple keyword reply can become risky when repeated webhooks, duplicate comments, deleted posts, moderation queues, and private reply eligibility are not tracked.
Growth teams want fast lead-magnet flows, but support and compliance teams still need to know which public comment caused the private path to open.
Instagram and Facebook comment surfaces are similar enough to group, but different enough that provider-specific constraints cannot be hidden from operators.

What bundle.social is building

Post-level rules let teams decide which posts, keywords, accounts, and campaign windows can trigger private follow-up.
The flow can support a public acknowledgement, private reply, or DM-style continuation where the provider supports that path.
Each execution needs idempotency, skipped-state tracking, provider response detail, and an audit record for the original comment.

For teams turning public comments into private intent

This waitlist is especially relevant for creator tools, lead magnet products, social commerce teams, giveaway workflows, and agencies that need safer comment-triggered follow-up.

Workflow

Workflow shape

The comment-to-DM flow starts at the post level, checks comment intent and eligibility, then records every public and private action taken.

01

Select eligible campaign posts

Choose which Instagram or Facebook posts can listen for comment keywords instead of applying one global rule everywhere.

02

Match the comment intent

Capture the keyword, comment, author, media, account, and campaign context that explains why the private path should start.

03

Send and record the follow-up

Attempt the supported private reply or DM-style action and store the result so teams can see sent, skipped, failed, or retried runs.

Implementation

Current status for comment to DM API

The comment to DM API workflow is in progress or private beta direction. The page is live now so teams can join the waitlist while bundle.social prepares broader access.

comment to DM API waitlist

Visitors should join the waitlist instead of expecting immediate public endpoint access for instagram comments, facebook comments, and keyword matching.

Select eligible campaign posts

Choose which Instagram or Facebook posts can 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.

Capabilities

Comment-to-DM features being shaped for early access

This page focuses on campaign-specific keyword workflows and private follow-up rather than broad social auto-reply automation.

Post-level keyword rules

Post-level rules let teams decide which posts, keywords, accounts, and campaign windows can trigger private follow-up.

Public-plus-private coordination

The flow can support a public acknowledgement, private reply, or DM-style continuation where the provider supports that path.

Duplicate and error control

Each execution needs idempotency, 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 should be able to decide which posts can trigger private replies instead of applying one global rule everywhere.

Keyword intent

The matched phrase should travel with the execution so support and growth teams know why a person entered the flow.

Auditability

Every public reply, private reply, skipped run, or provider error needs a clear status.

Supported surfaces

Instagram commentsFacebook commentsKeyword matchingPrivate repliesLead-magnet flowsExecution logs

Current limitations

  • Comment-triggered private replies depend on provider support, Meta permissions, account eligibility, and supported comment surfaces.
  • This workflow is not a generic outbound DM blasting workflow.
  • Teams will still need moderation and escalation paths when comments are sensitive, abusive, or ambiguous.
  • 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?

Not as public self-serve access yet. This early-access page collects interest from teams that need instagram comments, facebook comments, keyword matching, and private replies and want to shape the private rollout.

Who should join this comment to DM API waitlist?

Join if you are building a SaaS product, agency tool, AI agent, social inbox, or internal marketing workflow that needs instagram comments, facebook comments, keyword matching, and private replies. Use the note field to explain what you need from select eligible campaign posts.

How does this page relate to Social Media Comments API and Instagram DM API?

This page captures demand for comment to DM API while linking to related bundle.social surfaces that are already public or closer to the current product direction.

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.

What use cases should be shared on the waitlist?

Useful examples include downloadable lead magnets, creator welcome flows, giveaway responses, social commerce handoffs, or customer support paths that start from comment keywords.