The filter / condition node decides if and where your automation should continue. You can use it versatilely - from simple yes / no checks to complex branches.

How does the node work?

The filter / condition node always works the same way - you decide how to use it:

Basic principle:

You define one or more paths with conditions
The automation checks the paths from top to bottom
At the first fulfilled path → Automation takes this route
No path fulfilled? → "Else" path is taken

The "Else" path can either:

Lead to further nodes → Automation continues differently
Lead nowhere → Automation stops here

Typical usage patterns:

As a simple filter (stop logic):

Path 1: Assignment has no value → Automation continues
Else: Leads nowhere → Automation stops

With multiple branches:

Path 1: Label contains "VIP" → To account manager
Path 2: Label contains "Support" → To support team
Path 3: Label contains "Sales" → To sales team
Else: To general inbox

Simple yes/no switch:

Open path: Conversation time window is open → Send message node
Closed path: Conversation time window is closed → WhatsApp templates node

Important basic rules

1. Only ONE filter possible per path

You cannot filter for multiple different things simultaneously in one path (e.g. label AND contact list).

Wrong: One path with label equals "VIP" AND contact list equals "Premium" does not work.
Correct: Use two nodes one after another.
- Node 1 - Path 1: Label contains "VIP" → continue to Node 2
- Node 2 - Path 1: Contact list contains "Premium" → Execute action

2. Paths are checked from top to bottom

The automation checks each path in order and stops at the first match.

Example:

Path 1: Label contains "VIP"
Path 2: Label contains "Premium"
Path 3: Label contains "Support"

What happens if conversation has labels "VIP" and "Support"?

The automation goes to path 1, because that's checked first. Path 3 is no longer reached!

3. Understanding "has no value" correctly

This condition confuses many - here's the meaning:

"Assignment has no value" means: The conversation is NOT assigned (not assigned to anyone)
"Label has no value" means: The conversation has NO labels
"Contact list has no value" means: The contact is in NO list

Example:

If assignment has no value:
→ Assign the conversation to the Support team
Else:
→ Do nothing (since, in this case, the assignment has a value and so the conversation is therefore already assigned)

Available filter criteria

The most important criteria:

Contact Attributes

Contact attributes - First name, last name, email, phone + all custom contact attributes
Contact list - Which lists is the contact in?

Conversation Data

Label - Which labels does the conversation have?
Assignment - Who is the conversation assigned to?
Inbox - Which inbox is the conversation in?

Channel Data

Channel type - WhatsApp, Instagram, Facebook, etc.
Channel - Specific channel (e.g. WhatsApp number 1)

Time Data

Current date / time (from the time when the node is executed)
Current day of week (from the time when the node is executed)

Special Filters

Inbox opening hours - Open or closed
Conversation time window (important e.g. for WhatsApp 24h rule) - Open or closed
Message content - What's in the message?
Active other automations - Which automations are currently running?

All filter criteria in detail

Contact Attribute

Filter by all contact attributes:

System contact attributes: First name, last name, email, phone
Custom contact attributes: All individually created attributes of your workspace
Type: Depending on data type (text, number, date, etc.)

Contact List

Check if contact is in certain lists
Type: Multiple selection (contact can be in multiple lists)

Label

Check which labels the conversation has
Type: Multiple selection (conversation can have multiple labels)

Inbox

Check which inbox the conversation is in
Type: Single selection (conversation is always in only one inbox)

Assignment

Check who the conversation is assigned to
Type: Multiple selection (conversation can be assigned to multiple users)

Opening hours from inbox

Check if opening hours are currently active
Only 2 predefined paths: Open or Closed
Based on inbox opening hours settings

Conversation time window

Check if the conversation time window is open or closed
Only 2 predefined paths: Open or Closed
Important for WhatsApp: Only within the 24h window can you work with free messages, WhatsApp quick replies and lists, otherwise you must work with WhatsApp templates

Channel type

Check which channel type the conversation is running on.
Examples: WhatsApp, Instagram, Facebook, Telegram, email, live chat.
Type: Single selection.

Channel

Check which channel type the conversation is running through
Examples: WhatsApp, Instagram, Facebook, Telegram, Email, Live Chat
Type: Single selection

Current date / time

Check date / time of when this node is executed
Example: Only continue between 18:00-20:00
Type: Date / Time

Weekday

Check which day of the week this node is executed
Example: Only continue Monday-Friday
Type: Single selection

Active other automation

Check which automations are currently running on this conversation
Type: Multiple selection (multiple automations can be active simultaneously)
Important: The automation checking this condition excludes itself. "Has no value" therefore means no OTHER automations are currently running
Use case: Prevent duplicate execution

Message content

Check the content of a message (e.g. from the trigger)
Example: Message contains "Help" → Support flow
Type: Text

Conditions by data type

Each criterion has a data type that determines which conditions are possible.

Text

Available conditions:

begins with
ends with
contains
does not contain
contains none of
contains at least all these
contains at least one of
has any value
has no value
is equal to
is not equal to

Examples:

First name begins with "A"
Email contains "@gmail.com"
Message content contains at least one of "Help", "Support", "Problem"

Number

Available conditions:

has any value
has no value
is equal to
is greater than
is greater than or equal to
is less than
is less than or equal to
is not equal to
is between

Examples:

Age is greater than 18
Order value is between 100 and 500

Single Select

Available conditions:

has any value
has no value
is one of
is equal to
is none of
is not equal to

Examples:

Inbox is equal to "Support"
Channel type is one of WhatsApp or Instagram

Multi Select

Available conditions:

contains none of
contains at least one of
contains at least all these
has any value
has no value
is equal to
is not equal to

Examples:

Label contains at least one of "VIP" or "Premium"
Assignment contains at least all these: Max and Lisa

Explanation "contains at least one of" vs. "contains at least all these": Conversation has labels: "VIP", "Support", "Urgent"

"contains at least one of VIP or Premium" → Fulfilled (because "VIP" is present)
"contains at least all these VIP and Premium" → Not fulfilled (because "Premium" is missing)
"contains at least all these VIP and Support" → Fulfilled (both present)

Date

Available conditions:

has any value
has no value
is on
is after date
is past (is in the past)
is before date
is future (is in the future)
is between

Examples:

Contact attribute "Birthday" is on May 15
Contact attribute "Contract end" is future less than 14 days (expires in less than 14 days)
Contact attribute "Last interaction" is past more than 7 days (more than 7 days ago)

Date / Time

Available conditions:

has any value
has no value
is after date
is after time
is past
is before date
is before time
is future
is between
is between time

Examples:

Current date / time is between time 09:00 - 17:00
Contact attribute "Appointment" is after 14:00
Contact attribute "Last activity" is past more than 24 hours (more than 24 hours ago)

Filter Types

*Equals*	Will only trigger the automation if the received message is exactly the same as the filter word. Nothing less, nothing more. Just the exact value given.
*Doesn't equal*	Will trigger the automation every time the received message doesn't exactly match the filter word (e.g. filter word is "Superchat", every single received message that does not simply say "Superchat" can trigger the automation).
*Contains*	Will trigger the automation if the received message contains the filter word, even if other words are present.
*Doesn't contain*	Will trigger the automation if the received message doesn't contain the filter word at all (e.g. filter word is "Superchat", every single received message that doesn't contain "Superchat" within it will trigger the automation).
*Contains one of*	Allows you to choose multiple filter words and the automation will trigger if the received message contains one of those selected filter words (e.g. filter words are "Superchat" and “abc”, client types "1234 Superchat". Since it contains one of the filter words, it will trigger).
*Doesn't contain any of*	Allows you to choose multiple filter words, and the automation will only be triggered if the received message doesn't contain any of those words (e.g. filter words are "Superchat" and “abc”, client types "1234". Since it doesn’t contain one of the filter words, it will trigger).
*Starts with*	Will trigger the automation if the start of the message contains the filter word (e.g. if the filter word is "Super", then "Superchat is great" and "Superman is strong" will both trigger the automation).
*Ends with*	Will trigger the automation if the end of the received message contains the filter word (e.g. filter word is "Bye", client types "Goodbye", the automation will be triggered since the end of the message contains “bye”).
*Contains all*	Will trigger the automation if the received message contains all the selected filter words, and the order of the words is irrelevant. This does not mean one of the given words, but indeed all of them.
*Has any value*	Will trigger the automation when the client types anything. This is effectively the equivalent of having no filter at all.
*Has no value*	Will trigger the automation when a contact attribute has no value set. This is commonly used in automation stoppers - the message can only pass through the filter if the contact attribute "has no value". Once a value is set, future messages won't trigger the automation until the attribute is cleared again.