[FEATURE]: Implement Conditional (If/Else) Workflow Node

[amaan1114]

Feature Summary

Implement a Conditional (If/Else) workflow node that enables workflows to branch dynamically based on the output of previous nodes. This feature will allow users to create more flexible and intelligent automation workflows without requiring multiple separate workflows.

---

Problem Statement

AsyncNode currently executes workflow nodes sequentially and does not support conditional branching.

Without conditional logic, users cannot create workflows that make decisions based on previous node outputs. As a result, they must build multiple workflows or implement custom logic outside of AsyncNode to achieve common automation scenarios.

Examples include:

• Sending different notifications based on an API response.
• Processing successful and failed requests differently.
• Routing workflows based on user input.
• Executing different actions depending on AI model outputs.

This limits the flexibility and real-world usability of the workflow engine.

---

Proposed Solution

Implement a Conditional (If/Else) node that evaluates user-defined conditions during workflow execution and routes execution to the appropriate branch.

The implementation should include:

• A new Conditional node in the workflow builder.
• Support for configurable comparison operators (e.g., equals, not equals, greater than, less than, contains).
• Ability to evaluate outputs from previous nodes.
• Separate True and False execution paths.
• Integration with the existing workflow execution engine.
• Validation to prevent invalid workflow configurations.

The node should seamlessly integrate with the current workflow architecture and execution lifecycle.

---

Benefits

• Enables dynamic workflow branching.
• Supports more advanced automation scenarios.
• Reduces the need for duplicate workflows.
• Brings AsyncNode closer to modern workflow automation platforms.
• Improves the flexibility and scalability of the workflow engine.

---

Additional Context

• The implementation should follow the existing workflow engine architecture.
• Existing execution logging and monitoring should continue to function correctly.
• The design should allow future expansion to support more advanced expressions and logical operators.
• The workflow builder should clearly visualize both True and False execution paths.