Knowledge BaseAutomationIf Else Conditions
    Automation

    If Else Conditions

    Automation

    If/Else Conditions

    Introduction to Conditions

    Conditions allow your automations to make intelligent decisions based on contact data. Instead of treating all contacts the same way, you can create branching paths where different contacts receive different actions. Conditions are the "intelligence" in your automated workflows.

    How Conditions Work

    When your automation reaches a condition, Lead Fuel CRM evaluates whether the condition is true or false based on the contact's current data. If true, the automation follows the "Yes" path; if false, it follows the "No" path. You can have multiple conditions stacked to create sophisticated decision trees.

    Available Condition Types

    • Contact Has Tag: Check if the contact has a specific tag (e.g., "high-value-lead")
    • Contact Lacks Tag: Check if the contact does NOT have a tag
    • Contact Stage: Verify the contact's current pipeline stage
    • Custom Field Value: Evaluate custom field values (e.g., budget > $5000, service type = "package A")
    • Contact Source: Branch based on where the contact originated (web form, landing page, manual entry, etc.)
    • Time-Based: Execute actions only during business hours or on specific days
    • Contact Engagement: Branch based on email opens, link clicks, or appointment history

    Example: Service-Based Routing

    Imagine a form submission that captures which service a prospect is interested in. Your automation could check the "Service Interested In" custom field: if it equals "Website Design," send the website design follow-up email and assign to your web designer. If it equals "Logo Design," send a different email and assign to your branding specialist. This ensures prospects get relevant information immediately.

    Building Complex Decision Trees

    You can nest conditions within the "Yes" or "No" paths to create sophisticated workflows. For example: "If contact has tag 'hot-lead', check if they're in the sales stage. If yes, send premium follow-up; if no, move them to sales stage first." Complex trees should be documented so other team members understand the logic.

    Important: Avoid creating overly complex conditions that are hard to understand or maintain. If your condition tree has more than 3 levels, consider splitting into multiple automations.

    Tip: Use condition testing mode to preview how different contacts would flow through your automation before activation.

    Need more help? Contact Lead Fuel CRM support for personalized assistance.

    Have a question or want to connect with other Lead Fuel users? Join the Lead Fuel VIP Facebook Group