nodes / builtin / flow
If
Route items to different branches based on conditions
Formerly IF. The step was renamed in AWFlow 0.9; searching for the old name still finds it.
Send each item down a True or a False branch, depending on conditions you set.
Try it
Section titled “Try it”Price On Page Watch: a workflow with 6 steps, starting with When the price changes and ending with Remember this price.
What it does
Section titled “What it does”IF checks its conditions for every item that arrives. When they hold, the item leaves through the True port; otherwise it leaves through False. The item itself is not changed.
Each condition compares a value (usually an expression such as {{ $input.price }}) with another value, using an operator that fits the type you pick: String, Number, Date-Time, Boolean, Array or Object (for example Contains, Is Equal To or Is Not Empty). With several conditions, choose Match all (all must hold) or Match any (any one is enough).
Conditions in AWFlow 0.9
Section titled “Conditions in AWFlow 0.9”New If steps (version 2) build conditions as cards, one rule per card:
- Match all or Match any applies to a whole group of rules, and Add group nests a group inside another, so “A and (B or C)” is easy to read. AND / OR between cards is shown for you.
- Operators have plain names, grouped by type: is equal to, contains, matches pattern (advanced), length is… and so on. Lists and objects are compared by their content.
- Options › Type check: Loose converts values when it can (with a warning), Strict fails the step and names the rule and the item when a value has the wrong type. Ignore case compares texts without caring about capitals (an Aa ignored chip shows it).
- An empty date or number never counts as a date or as 0: the rule is false and the run log says why. An invalid pattern or date fails with “Condition N: …”.
Steps saved before 0.9 keep their rows, read top to bottom with each row’s own AND/OR. Update in the step’s header converts them to groups with exactly the same meaning. XOR means “exactly one of the two” (it used to behave like OR); it is only offered on rows that already use it.
When to use it
Section titled “When to use it”- Do something only for some items: “only send a message when the price dropped”.
- Take one of two paths: save new contacts, update existing ones.
- Stop a branch early: leave the False port unconnected and those items simply go no further.
For more than two paths, use Switch. To drop items without branching, use Filter.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Conditions (required) | Conditions | The conditions to evaluate. |
Outputs
Section titled “Outputs”-
True -
False
Each output item has these fields:
| Field | Type | What it holds |
|---|---|---|
| result | True/false | Whether the conditions held |
| inData | Any | The incoming data, unchanged |
{ "result": true, "inData": null}Port True is the top one and False the bottom one. Connect either or both.
Each output carries only its own items: the step on False gets the items that failed, never the true ones.
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
Example workflow
Section titled “Example workflow”- RSS Feed Read fetches new posts.
- IF checks that
{{ $input.title }}(String) Containsrelease. - True goes to a Slack node that posts the link. False is left unconnected.
Common issues
Section titled “Common issues”- “IF needs at least one condition.” Add a condition, or remove the node.
- Every item goes to False. Check the operator type. A number stored as text compares as text, so pick the type that matches the data (Number for prices), or convert it first with Edit Fields.
- The expression is empty. Open the input panel and pick the field instead of typing it, so the path matches the data that actually arrives.