Rules for Instagram automation.

Do this

Build rules around events Meta already sends the app.

• Reply to a comment keyword with one public reply and one private DM. Watch every post, one existing post, or the next post you publish.
• Reply to a story reaction, reply, or mention.
• Reply to a keyword in an open DM thread.
• Stay inside the messaging window.

Do not expect this

The official API is not a cold outreach tool.

• You cannot message people who never contacted you.
• You cannot scrape followers.
• You cannot bypass a block or a closed inbox.

Design around an invitation, not an audience list

A useful rule fulfills a request the person can understand. The caption names a keyword and says what arrives privately; the message delivers that item rather than switching to an unrelated sales pitch. Set Watch to every post and Reel, one existing post or Reel, or the next post or Reel. Turn a next-post rule on before you publish. Open Automations after you publish. DripDM attaches the rule to the earliest new post and shows a notice. Keep the distinction between public engagement and private messaging explicit. A follow, like, or profile view is not permission to start an API conversation. A comment provides an eligible private-reply path, and ordinary follow-ups require the recipient to respond. Consent to an email campaign is also a separate question from receiving a DM.

A workflow to try

A shop can invite people to comment SIZE for its sizing guide. The public reply explains where to look, while the first private message includes the guide and asks whether they have a fit question. Someone who responds can receive help in the active window. Someone who never responds should not enter an automatic promotional sequence. If the business wants an email address, explain the purpose in the lead-capture ask instead of disguising a subscription as required Instagram support.

Checks before you change the setup

Before enabling several rules, check that the same post and keyword are not being answered by another app or by Meta Business Suite. Test account selection, scope, message wording, and destination links with an independent account. Keep a human responsible for disputed prices, refunds, sensitive requests, and changes to the offer. Official API connectivity is a connection method; it is not a Meta badge, an endorsement, or a guarantee against enforcement.

A prelaunch review that separates responsibilities

Ask the content owner to verify the invitation and promised resource, the account owner to verify authorization, and the campaign operator to verify rule scope and delivery. Record the Watch choice: every post and Reel, one existing post or Reel, or the next post or Reel. For a next-post rule, confirm it is on before you publish, then open Automations and read the notice. If one person holds all three roles, still perform the checks separately. Include a privacy review when collecting information and a factual review when using AI. Decide who pauses a rule when an offer expires or a customer reports a misleading answer. This small division of responsibility is more practical than assuming the API connection certifies the entire campaign. Keep an ordinary contact route available for people who cannot receive the private response.