Conditions

Conditions – Create Simple Condition

Summary (SEO Meta Description):
The Conditions processor in WeHub evaluates simple conditions to control workflow execution.
Configure field name, type, and value to enable branching logic.

---

Overview

The Create Simple Condition action allows workflows to branch execution paths based on evaluated conditions.
It checks whether a field equals a value, matches a type, or is empty/not empty, and directs the workflow accordingly.

This is useful for implementing if/else logic, data validation, and conditional routing inside workflows.

---

⚙️ Configuration Options

Field	Type	Description
Label	String	Custom name for the node (e.g., "Check Consent Status").
Name	String	Field or variable name to evaluate.
Type	Enum	Data type or rule for evaluation. Options: STRING, NUMBER, BOOL, EMPTY, NOT_EMPTY.
Value	Any	Expected value (applies to STRING, NUMBER, BOOL).

---

💡 Example Use Cases

• Healthcare → Only send reminders if consent = true.
• Finance → Check if transactionAmount > 1000 before triggering alerts.
• Ops → Verify that a required field is not empty before calling an API.

---

FAQ

Q: Can I combine multiple conditions?
A: Yes, add multiple condition rows; all must be true for the condition to pass.

Q: What happens if a field is missing?
A: It evaluates as EMPTY unless explicitly set otherwise.

Q: Can I use this for branching?
A: Yes, workflows can branch based on true/false outcomes of the condition.

---

Keywords: WeHub Conditions, Create Condition, workflow branching, if else, simple rule