Instagram DM automation, end to end.

The triggers

Each rule has one job.

• A comment keyword on a post or Reel, with a public reply and a private DM. Watch every post, one existing post, or the next post you publish.
• A story reply, reaction, or mention.
• A keyword in an existing DM.
• On Pro: a follow gate, a reminder, a scheduled send, product cards, and older comments.
• On Growth: an AI reply from your notes.

What it will not do

It will not message someone who never contacted you. It will not store your Instagram password. It will not send a scheduled DM after the messaging window closes.

A first week

Connect one account. Ship one keyword. Read the taps. Add a second rule only after the first one is clear.

Build a small system with clear ownership

A complete DM workflow starts before the rule: a public invitation sets the expectation, a trigger carries the customer action, a match selects the response, and an eligible send fulfills the request. A comment rule watches every post and Reel, one existing post or Reel, or the next post or Reel after the rule is on. DripDM provides that reply layer alongside captured contacts, lead information, link-tap tracking, and bio pages. Keep the downstream booking, commerce, or email system identifiable because a sent destination is not a completed transaction. Each step has one purpose you can test.

A workflow to try

Begin with a single resource campaign. Prepare the destination, print the same keyword in the caption and rule, and send a useful first private reply. Test from an independent account, inspect requests, and open the link on mobile. Read the first threads before adding complexity. Pro can add gates, a nudge, scheduling, Pages, and product cards; Growth can add optional AI for varying questions. Add each only after the simpler flow works and its customer purpose is clear.

Checks before you change the setup

Separate product allowances from platform eligibility. Free has its own DM, contact, and lead caps; paid plans do not cap those product quantities, but Meta still controls API sending. A comment grants one private reply and the recipient’s response opens ordinary follow-up permission. An official connection is not a guarantee of account safety. Monitor holds and rejected sends alongside taps, and keep a human responsible for exceptions instead of treating every quiet rule as a reason to send more.

An operating model for the next campaign

Keep one owner for the offer, one review process for rule changes, and a clear source for downstream confirmations. Save the working caption, matcher, opening text, destination, and independent test result together. When adding a second rule, identify its distinct event and purpose so it does not duplicate the first response. If you add AI, preserve the static baseline and review both paths. If you add another platform, test it separately. A small durable operating record lets the business understand what is live and who maintains it, instead of accumulating automations whose links, facts, or permissions nobody checks after the initial launch.