WorqHat
Process Nodes

If Else Condition

Category
Logic & Control Flow
Node Type
Conditional Branching

Overview

The If/Else Condition node helps you create conditional logic branches in your workflow. It checks a condition you define and then decides which path to take — True or False — based on the result.

This allows you to make your workflow “think” and automatically handle different situations. For example, you can send a message only if the sender’s email matches a specific address, or trigger a notification only if a value meets certain criteria.

Description

Control workflow decisions based on data.

This node compares one piece of data (like an email address, name, or number) against a value you choose. Depending on whether the condition is true or false, the workflow continues along the True path or the False path.

True Path

The workflow follows this path if the condition is met (e.g., Email equals "admin@example.com").

False Path

The workflow follows this path if the condition is NOT met.

It’s commonly used to filter data, control decisions, and automate actions based on user input.

Input Parameters

The If/Else Condition node accepts settings to define the comparison logic.

Source NodestringRequired
The node that provides the input data to check.
Example
"Send Mail"
ParameterstringRequired
The specific data field to evaluate.
Example
"senderEmail"
OperatorstringRequired
The comparison method to use.
Example
"Equals", "Not Equals", "Contains", "Greater Than"
ValuestringRequired
The value to compare against the selected parameter.
Example
"admin@example.com"
Node DescriptionstringOptional
An optional text field to describe what this condition checks.
Example
"Check if sender is admin"

Output Parameters

The node returns a boolean result indicating which path was chosen.

conditionbooleanOptional
Shows whether the defined condition evaluated to true or false.
Example
true
Next StepstringOptional
Indicates which path the workflow will follow next.
Example
"Send Welcome Email"
Logic Flow
  • True: The condition matched. Workflow follows the True path.
  • False: The condition did not match. Workflow follows the False path.

Output Type

Output Type: Boolean

The output is a simple true or false value that determines the immediate next step in the workflow execution.

Example Usage

Example 1: Check Sender Email

Verify if an email comes from a specific address.

{  "sourceNode": "Send Mail",  "parameter": "Input: senderEmail",  "operator": "Equals",  "value": "admin@worqhat.com"}
{  "condition": false,  "Next Step": "Return to Default Path"}

Explanation: The sender was not "admin@worqhat.com", so the result is False.

Example 2: Match User Name

Check if the user's name is "Alex".

{  "sourceNode": "User Info",  "parameter": "Input: userName",  "operator": "Equals",  "value": "Alex"}
{  "condition": true,  "Next Step": "Send Welcome Email"}

Explanation: The name matched "Alex", so the result is True.

How to Use in a No-Code Workflow

1

Add the Node

Drag and drop the If/Else Condition node into your workflow editor.

2

Connect Source

Choose the previous node that provides the data to check (e.g., "Send Mail").

3

Select Parameter

Pick the data field to evaluate (e.g., senderEmail).

4

Define Condition

Select an Operator (e.g., Equals) and set a Value to compare against.

5

Connect Paths

Connect the True path to the action for a match, and the False path for no match.

6

Run Workflow

Run the workflow. The node will automatically route execution based on the result.

Best Practices

  • Use clear, descriptive names for your nodes to make the logic easy to follow.
  • Double-check that the parameter exactly matches the field name from your source node.
  • Always test your workflow with both True and False outcomes.

Do / Don’t

Do
  • ✔️ Use Contains for partial matches (e.g., checking if email contains "@gmail.com").
  • ✔️ Group related conditions together for complex logic.
  • ✔️ Handle the False path gracefully (e.g., log an error or end the workflow).
Don’t
  • ❌ Don’t forget that string comparisons can be case-sensitive.
  • ❌ Don’t leave the False path disconnected if an action is required in that case.
  • ❌ Don’t compare incompatible types (e.g., text vs number) without verifying formats.

Common Errors

Parameter not foundErrorOptional
The selected parameter doesn't exist in the source node. Check spelling.
Invalid OperatorErrorOptional
An unsupported operator was selected.
Value missingErrorOptional
The comparison value field is empty.
Always FalseWarningOptional
Data type mismatch (e.g., '123' string vs 123 number) or incorrect input.

Example Workflow Integration

Use Case 1: Email Filter

Auto-reply only to specific senders.

  1. Trigger: Receive Email.
  2. If/Else Node: Check if senderEmail equals vip@client.com.
  3. True Path: Send "Priority Response" email.
  4. False Path: Send standard auto-reply.

Workflow Data Flow:

{{email.sender}} →  {{ifElse.parameter}}

Use Case 2: VIP User Check

Grant access based on user status.

  1. Fetch Data: Get user profile.
  2. If/Else Node: Check if plan equals premium.
  3. True Path: Unlock exclusive content.
  4. False Path: Show upgrade prompt.

Workflow Data Flow:

{{user.plan}}    →  {{ifElse.parameter}}