Skip to content
The Social Tools The Social Tools Docs

Conditions reference

Conditions (the tests a branch runs against each comment) decide whether a Workflow branch matches. There are four condition types: Keywords, Author, Platform, and Sentiment.

Three answers up front, because they cover most questions:

  • Case sensitivity: Keywords and Author matching is case-insensitive. “FREE” matches “free”.
  • Partial words: Keywords and Author match on substring, not whole word. “win” matches “winning”.
  • Regex: Not supported. No condition type accepts regular expressions. See Regex support.

A branch matches only when all of its conditions match — conditions are AND’d together. For how branches and Workflows are ordered and which one wins, see How workflows work.

Pick a condition type from the branch editor's Condition type dropdown.

Keywords

Section titled “Keywords”

Matches when the comment text contains one or more keywords you list.

Matching semantics:

  • Case-insensitive. Both the comment and each keyword are lowercased before comparison, so “Scam” matches “scam”.
  • Substring, not whole word. A keyword matches if it appears anywhere in the comment text. “win” matches “winning” and “drawing”. There is no word-boundary option.
  • Match mode. A radio control sets how multiple keywords combine: Match any (any, the default) matches when at least one keyword is present; Match all (all) requires every keyword to be present.
  • Unicode and emoji. Case folding is Unicode-aware, so accented and non-Latin letters fold correctly (for example “É” matches “é”). Emoji and CJK characters match literally as substrings.
  • No Unicode normalization. Composed and decomposed forms of the same character are not treated as equal. A keyword typed with a precomposed “é” (U+00E9) will not match a comment where the same letter is written as “e” + combining accent (U+0065 U+0301), and vice versa.

You add keywords one at a time — type a keyword and press Enter to turn it into a chip.

Input comment
promo_bot_88 Facebook

Check out my FREE giveaway 🎉 link in bio!

Matched condition
Keywords: "free", "giveaway" (Match any)
Resulting action Flag

Match any fires because at least one keyword (both, here) is present. Flag hides the comment on-platform and sends a push notification. Reversible via Allow.

Edge cases:

  • Empty keyword list. A Keywords condition with no keywords always matches. It never blocks a branch — the branch behaves as a catch-all for that condition.
  • Substring surprises. Because matching is substring-based, short keywords match inside longer words. “ass” matches “class” and “assist”. Use longer, more specific keywords to avoid false matches.
  • Match all is strict. With Match all, a comment missing even one of the listed keywords does not match.

Author

Section titled “Author”

Matches on the comment author’s display name.

Matching semantics:

  • Case-insensitive substring. The condition matches when the author’s display name contains the text you enter, ignoring case. The in-app helper reads: “Matches authors whose name contains this text (case-insensitive).”
  • Single pattern. You enter one text value, not a list.
Input comment
Daily Promo Deals Instagram

DM me for wholesale prices

Matched condition
Author contains "promo"
Resulting action Flag

"promo" is a substring of "Daily Promo Deals" (case-insensitive), so the branch matches.

Edge cases:

  • Empty pattern. An Author condition with no text always matches.
  • Substring only. The match is a plain substring test on the display name. The field placeholder shows examples like "john*" and "@johndoe", but wildcards and handle syntax are not special — the characters are matched literally. Entering john* looks for the literal substring john*, which will rarely match. Enter the plain text you expect to appear in the name (for example john).
  • Display name, not handle. Matching runs against the stored author display name.

Platform

Section titled “Platform”

Matches when the comment came from the selected platform.

Matching semantics:

  • Exact match, not substring. Unlike Keywords and Author, Platform is an exact equality check against the comment’s platform (case-insensitive on ASCII letters). It does not do substring matching.
  • Choose from enabled platforms. You pick the platform from radio tiles showing the platforms enabled for your setup.
Input comment
someone Instagram

Love this post!

Matched condition
Platform is Instagram
Resulting action Allow

The comment is from Instagram, so the condition matches. A Facebook comment would not match this branch.

Edge cases:

  • Empty platform. A Platform condition with no platform selected always matches.
  • Use Platform to scope by network. Combine a Platform condition with other conditions (they are AND’d) to run workflows only on, say, Instagram comments.

Sentiment

Section titled “Sentiment”

Matches when the comment’s detected sentiment equals the sentiment you choose and the detection confidence is at or above your threshold.

Matching semantics:

  • Sentiment value. Choose one of positive, negative, or neutral.
  • Confidence threshold. A “Confidence threshold” slider (0–100) sets the minimum confidence. The condition matches only when the detected label equals your chosen sentiment and confidence is at or above the threshold. The in-app helper reads: “Matches comments with the selected sentiment when confidence is at or above the threshold.”
  • Where the sentiment comes from. If a sentiment label and confidence were already computed for the comment, those are used. Otherwise the comment text is analyzed on the spot by an internal keyword-lexicon analyzer.
Input comment
unhappy_customer Facebook

This is the worst service I have ever used. Total scam.

Matched condition
Sentiment is negative, confidence ≥ 70
Resulting action Flag

The comment reads as negative above the 70 threshold, so the branch matches and flags it for review.

Edge cases:

  • Empty sentiment. A Sentiment condition with no sentiment selected always matches.
  • Threshold trade-off. A high threshold reduces false positives but misses borderline comments; a low threshold catches more but risks mislabeling. Tune it against your own comments.
  • Exact label match. The detected label must equal your chosen sentiment exactly. A “neutral” comment does not match a branch set to “negative”, regardless of confidence.

Regex support

Section titled “Regex support”

Regex is not supported. None of the four condition types accept regular expressions. There is no regex condition type, and Keywords and Author treat everything you enter as literal text (case-insensitive substring). Special characters such as *, ., (, and \ have no special meaning — they are matched as literal characters.

To approximate patterns, use several keywords with Match any, or use shorter substrings (remembering that matching is not whole-word).

How conditions combine

Section titled “How conditions combine”

Within one branch, all conditions must match — they are AND’d. Add a Keywords condition and a Platform condition to the same branch, and the branch matches only comments that satisfy both.

A branch with no conditions always matches, acting as a catch-all. To understand which branch and which Workflow ultimately fires when several match, see How workflows work.

Section titled “Related”
  • How workflows work — branch and Workflow ordering, first-match-wins, and how conditions combine.
  • Actions reference — what Flag, Allow, Delete, Reply, and the other actions do.
  • Testing workflows — preview which branches match a comment before going live.