Conditions and Rules in Instagram DM Automations
Conditions and rules in Instagram DM automations are different layers. A comment keyword is a trigger. A condition node runs later on a tag, a collected field, or a reply. Keyword match types already live in keyword match types — this page will not rebuild that tutorial. Branching that uses conditions is branching logic.
The trigger starts the automation (comment, Story, DM keyword). A condition chooses the next step after something is known. Mixing them is how you debug at midnight. Put the filter as early as you can: if only one Reel should fire, scope the rule to that media. Do not wait for a condition ten nodes later.
Trigger versus condition, in one table
| Layer | Decides | Examples | If you get it wrong |
|---|---|---|---|
| Trigger | Who enters the automation | Comment keyword LINK on Reel A; Story reply BOOK; inbound DM PRICE | Wrong media fires, or nobody enters |
| Match type | How the trigger word is read | Exact SIZE vs contains size | Hearts match, or “size 28” misses — see match-types article |
| Condition | Which node after something is known | Tag=wholesale; reply is 1 vs 4+; follow-gate passed | Everyone gets the same URL anyway, or the graph dead-ends |
Do not use a condition to fake media scoping. If Reel B should never send the lookbook, do not start the automation on all media and hope a later node checks the caption. Scope the rule. Conditions are for facts you learn after entry.
Put the filter as early as you can
If only one Reel should fire, scope the rule to that media. If only followers should get a file, that is a follow-gate node, not a caption essay. If only wholesale buyers should get the line sheet, do not teach LINE on a consumer Reel. Teach it on the B2B lookbook, or require a tag you set when they already qualified.
Midnight debug usually looks like: catch-all trigger + six conditions trying to undo it. Invert the design. Tight trigger, few conditions, explicit else. DM automation is easier to pause when the rule name includes the media.
Conditions that are honest
- Tag equals wholesale (you set that tag on purpose earlier).
- They answered “team” vs “solo” in the words you asked for.
- Follow-gate passed (Meta’s follow field after they tap I’m following).
- Collected email exists if the next step is “send the issue.”
Conditions that are not honest: guessing country from emoji flags, inferring budget from compliment density, “if message is long then enterprise.” Long messages go to fallback or human. Do not build a personality test. Agencies should forbid clever conditions a client cannot explain.
Rules you will actually maintain
A rule is the named automation: trigger + graph + destination. When the post dies, pause the rule. When the SKU dies, edit the DM or pause. When the cohort fills, switch ENROLL to WAITLIST. Conditions inside a dead rule still run if the trigger still matches leftover comments — which is why scoping and pausing beat clever elses.
- Name the rule with client or brand, media, keyword.
- Set the trigger (and match type) as tight as the caption you taught.
- Add a condition only if a later fact changes the URL or queue.
- Add an else that is not checkout.
- Calendar the pause.
Story triggers die with the Story
A Story reply trigger is still a trigger. When the Story expires, new replies stop. Leftover mention rules do not expire unless you pause them. Do not use a condition “if Story is live” as a substitute for pausing mention automations with dead URLs. You pause.
What this page will not claim
No Live comment trigger. No Trial Reels mode. No Click-to-DM ads trigger. No HubSpot-native condition. You can HTTP-request a system you own; that is not a Salesforce product. You can tag and hand off. Keep the vocabulary small: trigger, match, condition, else. If a pitch deck needs more nouns, it is probably selling a maze.
Midnight debug is usually a wide trigger plus six conditions trying to undo it
Invert the design. Tight trigger, few conditions, explicit else. If only one Reel should fire, scope the rule to that media. Do not start on all media and hope a later node checks the caption. Conditions are for facts you learn after entry: a tag you set on purpose, a reply in the words you asked for, follow-gate passed, collected email exists if the next step is “send the issue.”
Match type sits on the trigger word. Exact SIZE versus contains size is not a later condition — that tutorial lives on the match-types article. Mixing trigger and condition in one sentence is how you debug at midnight. Put the filter as early as you can. Name the rule with media so a tired operator can pause it.
Honest conditions versus personality tests
- Honest: tag equals wholesale because a previous node set it; they answered “team” vs “solo”; follow-gate passed; email collected.
- Not honest: country from emoji flags, budget from compliment density, “if message is long then enterprise.” Long messages go to fallback or human.
- Do not build a personality test. Agencies should forbid clever conditions a client cannot explain.
- A condition on a tag marketing forgot to apply will send everyone the consumer URL. Set tags on purpose, then branch.
When the post dies, pause the rule. Conditions inside a dead rule still run if the trigger still matches leftover comments — which is why scoping and pausing beat clever elses. When the SKU dies, edit the DM or pause. When the cohort fills, switch ENROLL to WAITLIST. Story reply triggers stop getting new replies when the Story expires; leftover mention rules do not expire unless you pause them. Do not use a condition “if Story is live” as a substitute for pausing mention automations with dead URLs.
A maintainable rule in five steps
- Name the rule with client or brand, media, keyword.
- Set the trigger (and match type) as tight as the caption you taught.
- Add a condition only if a later fact changes the URL or queue.
- Add an else that is not checkout.
- Calendar the pause.
If only followers should get a file, that is a follow-gate node, not a caption essay. If only wholesale buyers should get the line sheet, do not teach LINE on a consumer Reel. Teach it on the B2B lookbook, or require a tag you set when they already qualified. A single lookbook link needs trigger, send, optional public line. Stop. You do not need conditions.
Nouns this page will not add to a pitch deck
No Live comment trigger. No Trial Reels mode. No Click-to-DM ads trigger. No HubSpot-native condition. You can HTTP-request a system you own; that is not a Salesforce product. You can tag and hand off. Keep the vocabulary small: trigger, match, condition, else. If a pitch deck needs more nouns, it is probably selling a maze. CommentLink is easier to pause when the rule name includes the media. The wrong post fired? Usually the trigger was too wide (all media, catch-all). Fix the rule scope before adding nodes.
FAQ
What is the difference between an Instagram trigger and a condition?
The trigger starts the automation (comment, Story, DM keyword). A condition chooses the next step after something is known.
Should I use a condition instead of scoping media?
No. Scope the rule to the Reel. Conditions are for facts after entry.
Where do match types sit?
On the trigger word. Exact versus contains is not a later condition. See the match-types article.
Can a condition check Salesforce?
Not natively. Tags, collected fields, replies, follow-gate. HTTP if you build it — not a native CRM product.
Why did the wrong post fire?
Usually the trigger was too wide (all media, catch-all). Fix the rule scope before adding nodes.
Do I need conditions for a single link drop?
No. Trigger, send, optional public line. Stop.
Should I use a condition instead of scoping the Reel?
No. Scope the rule to the Reel. Conditions are for facts after entry. A later caption-check is how you debug at midnight.
Can a condition check Salesforce or HubSpot?
Not natively. Tags, collected fields, replies, follow-gate. HTTP if you build it — not a native CRM product.
The Story expired but people still get last month’s drop URL. Condition it?
Pause the mention rule. Do not fake “if Story is live.” Leftover mention automations do not expire by themselves.
Related reading
See Instagram DM automation
Comments, Stories, keywords, follow-gates, lead capture and a shared inbox — official Meta APIs.
See DM automation