Automation
Comment-to-DM automation
Turn comments into conversations: keyword matching, public replies, dedup rules, and what commenters actually experience.
How it works
You tell people to comment a keyword. When a comment lands, Ravela checks it against your trigger — the keyword, the post it’s on, and whether this person already got a response on this post. If it matches, your flow sends its opening DM. Only after Instagram accepts that send does Ravela post the optional public reply on their comment.
From the commenter’s side it feels effortless: they comment “GUIDE,” Instagram accepts the promised message, and then your public reply appears under their comment.
Configure the trigger
Everything below lives in the trigger’s conditions step (Automations → Triggers → Post or Reel Comment):
- Which posts — all posts and reels, specific ones you pick from your media gallery, or “next post” to arm the one you’re about to publish.
- When to fire — on any comment, or only when specific keywords appear. Matching is Contains (anywhere in the comment) or Exact (the whole word).
- Reply publicly too — post a public reply under the comment alongside the DM. Add up to six variations and Ravela rotates through them, so your comment section doesn’t repeat itself; an optional delay makes replies feel less instant.
- Once per post per person — on by default. Each person gets one response per post no matter how many times they comment. Turn it off only if you genuinely want every matching comment to re-fire the flow.
- Finishing touches — restrict to followers or verified accounts, and optionally have the account like the comment as part of the response.
The public reply, done honestly
The public reply is more than decoration — it tells the commenter (and everyone reading) that the DM was sent. Ravela posts it only after Instagram accepts the matching flow run’s outbound send. If the person opted out, the send was blocked, or Instagram rejected it, Ravela stays quiet rather than making a promise after a known failure.
Instagram also caps how many comment replies an account can post per hour (roughly sixty). If a viral moment exceeds that, Ravela retries replies as capacity frees up — the DMs keep flowing in the meantime.
Who gets the DM
A comment is an interaction, not a message — and Instagram is strict about the difference. A normal DM is only allowed within 24 hours of someone’s last message to you, and commenting does not open that door.
Instagram’s answer is the private reply: one DM sent in reply to the comment itself, allowed for seven days after it was posted — even if that person has never messaged you. Ravela sends your opening DM that way whenever the 24-hour window isn’t already open, so a first-time commenter and a follower you haven’t heard from in months both get your message.
One rule is worth designing around: Instagram allows exactly one private reply per comment. Make the opening Message node text, with optional quick replies, or use Ask Input for a text prompt that waits for their answer. Text plus quick replies travels as that single private reply; tapping one counts as the commenter’s response, opens the normal 24-hour window, and lets the rest of the flow continue.
Put media, carousels, URL buttons, checkout or delivery steps after that response. If one of those runs before the commenter replies, Ravela stops the run instead of attempting a message Instagram does not permit yet.
Ravela also shows an amber warning in the flow builder and anywhere you attach an affected comment trigger. It points out paths that can reach rich content or a second DM before the commenter responds. The warning does not block publishing, because the same flow can still be valid for a DM trigger or for a returning commenter whose normal DM window is open.
This rule belongs to the trigger run, not the saved flow. If you reuse that same flow for a DM Keyword trigger, the person’s keyword message has already opened the normal window, so rich opening steps can send normally.
One habit pays for itself here: pick a short, memorable, single-word keyword and say it out loud in the post. “Comment GUIDE” outperforms “comment if you want me to maybe send it.”
Keep an eye on it
Every fire shows up as a run on the flow’s Runs page, including skips and their reasons — opt-out, expired comment, reused private reply, or a rich step that ran before the commenter replied. If a commenter says they didn’t get the DM, the run log tells you why in one click.