Conditions: operators, relative dates, messages and language
Conditions decide whether a run carries on and which path it takes. You write them on the record’s fields, or on the message, the email and the reply, with operators for text, numbers and relative dates.
Where are conditions used?
In Settings → Only records that…, in the Choose a path step, and in the automation’s goal.
“And” and “Or”
In Only records that…, every rule must match. In a path of Choose a path, the rules are joined with And…, so all of them must match too. To accept one case or another, add a path for each case and lead the paths to the same step.
Operators
Comparing the text of messages and emails ignores upper and lower case.
Relative dates
Units: minutes, hours or days. A date-only field accepts days only. Every operator needs a duration greater than 0, except is today.
Dates are read in the workspace’s time zone, or in the trigger’s own time zone with On a schedule and Before or after a date.
Special fields available in conditions
Message language
Corteksa detects the language of the message itself: Arabic, English, French, Turkish, Spanish, German, Russian, Persian, Urdu and Hindi. A short or unclear message, such as “ok” or “👍”, is read as “Unknown”, and you can branch on that too.
People conditions
A condition on the assignees or the creator compares the people themselves, and is on the assignees means “is among them”. If the chosen person has left the workspace, the condition fails whatever the operator, so nothing gets through by mistake.
Missing context
In a run with no message, the message field doesn’t exist: is fails and is empty passes.
If something goes wrong
A real example
Messages in Arabic and English arrive on the same number.
- Choose a path: an “Arabic” path with the condition that the message language equals Arabic.
- An “English” path with the condition English.
- Everyone else: reply in Arabic and English together.
Every client gets the reply in their own language.