IF Node

The If Condition node creates different execution paths in your workflow based on logic rules you define. Think of it like a fork in the road — depending on whether your conditions are met, your workflow takes one path or another.

For Example: You might want to send negative mentions to your PR team but positive mentions to marketing. The If Condition node checks the sentiment and routes the workflow accordingly

How Conditions Work

You can create simple or complex conditions using two logical operators:

  • AND – All conditions must be true for the path to execute.

  • OR – Any one of the conditions can be true for the path to execute.

Building Conditions

When you configure an If Condition node, you'll define what to check and what value it should match. Common condition types include:

  • Text matching: Check if a field equals, contains, or starts with specific text.

  • Number comparisons: Check if a number is greater than, less than, or equal to a value.

  • Boolean checks: Check if something is true or false

  • Empty/exists checks: Check if a field has a value or is empty.

You can combine multiple conditions using AND/OR logic to create sophisticated routing rules.

Use Cases

  • Sentiment-based routing - IF sentiment is "negative" AND the author has more than 10,000 followers → Notify PR team immediately. ELSE → Log for weekly review. This ensures high-visibility negative mentions get immediate attention.

  • Sales signal detection - IF competitor is mentioned OR pricing is discussed → Send to sales team in Slack. This catches buying intent signals from multiple indicators.

  • Severity-based workflows - IF signal severity is "High" → Create urgent ticket and notify executive team. ELSE IF severity is "Medium" → Add to regular queue. ELSE → Log for reference. This ensures the right people see the right issues.

  • Lead qualification - IF company size > 500 employees AND industry = "Technology" → Add to high-value pipeline. This automatically qualifies leads based on your ideal customer profile.

  • Content filtering - IF post contains profanity OR is flagged as spam → Ignore. ELSE → Process normally. This keeps your workflow clean from irrelevant content.

Tips for Effective Conditions

  • Start simple: Begin with one or two conditions and test them. You can always add more complexity later.

  • Use Boolean outputs: When possible, have your AI agents return simple True/False values (like "Buying Intent: True"). This makes your conditions cleaner and easier to understand.

  • Think about the "else" path: Always consider what should happen when conditions aren't met. Sometimes doing nothing is fine, but often you want a fallback action.

  • Test edge cases: Run your workflow with different types of data to make sure your conditions work as expected in all scenarios.

Pro tip: Use Boolean outputs from agents (e.g., "Buying Intent: True/False" or "High Priority: Yes/No") to simplify your conditions. Instead of checking multiple fields, you can just check one True/False value that the agent has already determined for you.