Quick links
What is the criteria filter node?
You can build and edit powerful criteria to filter out recipients using the criteria builder in the criteria split node.
What is the criteria filter node?
The criteria split node lets you split recipients into two paths, meeting the criteria you specify (the success path), and those that don’t (the fail path).
The criteria builder supports multiple types. You must select the correct type for the value.
The UI does not validate the criteria builder yet. If an incorrect type is used, or there is an error in the formula, the flow will not run correctly.
Formula
Currently formulas can only be entered (as free text) on the left or right hand side of an equality operator when the ‘formula’ type is selected.
The following formulas and arguments are currently supported:
DateAdd("interval", number, instant)
- Returns the result of adding the number of intervals to the given instant (e.g. add 5 days from now)
interval
— SECONDS, MINUTES, HOURS, DAYSnumber
— The number of intervals to add (e.g. 5)instant
— The instant to add to (a moment in time)
Now()
- Returns the current datetime
instant
In our above example, to use a formula that specifies ‘add 5 days from now’ you would enter: DateAdd("DAYS", 5, NOW())
ExperienceStart()
- Returns the
instant
the experience started (when the flow triggers for an individual recipient)
Field
The field
option allows you to use field paths that point to other data within the flow; the syntax is the same as merge fields but without the use of the curly brackets {{}}
.
For example, if City
was a column in your CRM, you could use the field type and add the value inboundSMSTrigger_1.inarguments.[0].City
to split your recipients down different paths.
Learn about building field paths here
Boolean
Boolean value type can be either true or false.
String
A string type is just a normal text string - for example, in the LHS you may have the field City
defined as above, in the RHS of the builder you might put Sydney
as the string value.
Number
A simple integer, e.g. 1234.
Examples
Offer expiry example
As an example, we can use the criteria split to create an offer expiry period in the flow.
When a recipient replies to the original outbound SMS, the reply will come back into Pendula, and the split will check whether it was received before the expiry - i.e. was it received 2 days before or 2 days after the original messages sent?
In the criteria builder:
-
LHS Select type =
formula
-
Enter the formula =
DateAdd ("DAYS", 2, ExperienceStart())
(2 days from when the experience started)
-
Select operator =
less than
-
RHS Select type =
formula
-
Enter the formula
Now()
Essentially this criteria checks that the flow was triggered less than 2 days ago and the recipient has replied, they can continue through the the ‘success’ path of the split.