Conditions

Condition nodes check something and send the flow down one path or another. There are two: Condition (data and time rules) and Working Hours Condition (your opening hours).

Condition (condition)#

Add one or more rules with the ADD CONDITION chips. The node has two outputs, True and False.

Field	What it does	Default
Match	Appears with two or more rules. AND = every rule must pass; OR = any rule.	AND
Rules	Each rule has a type, an operator and a value (below).	—

The contact is re-read just before the check, so changes made earlier in the same flow count. A condition with no rules returns False. Compare values are typed in as-is — variables aren't resolved inside them.

Rule types#

Type	What is compared	Operators in the builder	Value
Customer Attributes	A custom attribute's value on the contact (empty if the contact doesn't have it)	equals, not equals, contains, starts with, ends with, is set, is not set	Text (not needed for is set / is not set)
Country Code	The contact's phone country code, without the +	equals, not equals	Pick from the list (for example 91, 971, 1)
Date Time Format	The current date/time, formatted with the pattern you choose, in the workspace timezone	equals, not equals, contains	Text in that format
Timezone	The current time (HH:mm) in the timezone you pick	greater than, less than, equals, not equals	A time such as 09:00
Time Variables	The current date, time or day of week	equals, not equals, greater than, less than	Matches the subtype: a formatted date/time, or a weekday name (Monday–Sunday)

Comparisons ignore upper/lower case and surrounding spaces. Changing the operator clears the value.

Date and time formats#

Patterns use these tokens: YYYY year, MMMM / MMM / MM month, DD / D day, HH / hh / h hour, mm minutes, ss seconds, A AM/PM.

• Dates: DD/MM, MM/DD, DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY, DD.MM.YYYY, D MMM YYYY, MMM D, YYYY, MMMM D, YYYY, D MMMM YYYY
• Times: hh:mm A, hh:mm:ss A, h:mm A, h:mm:ss A, HH:mm, HH:mm:ss
• Date and time: combinations such as YYYY-MM-DD HH:mm and DD/MM/YYYY hh:mm A

The workspace timezone is the one in your working-hours settings (UTC if none is set). The Timezone rule has its own list of 60+ timezones, default UTC.

Tips for time rules#

• For greater than / less than on dates, use YYYY-MM-DD — day-first formats such as DD/MM/YYYY can be read month-first when ordered, and formats without a year can't be ordered reliably.
• Use equals for day of week; ordering weekday names alphabetically isn't meaningful.
• To run something only on weekends, use two rules with OR: day equals Saturday, day equals Sunday.

Activation errors#

No rules, a blank operator or value (except is set / is not set), an attribute that was deleted, or a blank format on a date/time rule. An unconnected True or False output is a warning.

Working Hours Condition (working_hours_condition)#

Checks the current time against a working-hours schedule. Three outputs:

Output	When
During Working Hours	Now falls inside an open range for today
Outside Working Hours	Otherwise
On Holidays	Today is a special day marked closed (with no open ranges)

Field	What it does	Default
Check against	Organisation Working Hours, or a custom schedule by name.	Organisation Working Hours

• Hours are evaluated in the schedule's own timezone (UTC if none). A time is "during" when it's at or after the opening time and before the closing time.
• A special day with its own ranges replaces the normal weekday hours; a special day with no ranges counts as a holiday.
• If no working hours are configured at all, or the organisation schedule is switched off, the node always takes During (an activation warning tells you).
• If the chosen custom schedule is deleted, activation fails with an error.

What's next#