Filters

A conditional gate that evaluates data against a set of rules. If conditions are met the workflow continues; if not, execution stops.

Workflow Node Conditional Logic Group-based Rules

What is the Filter node?

The Filter node is a conditional gate in a Konnectify workflow that evaluates incoming data against a set of conditions. If the conditions are met, the workflow continues. If they fail, execution stops at that point.

Filters use a group-based condition system: conditions are organized into groups, each group can match ALL or ANY of its conditions, and groups are combined with AND or OR operators.

What Filters let you do

Gate workflow execution based on field values
Combine conditions with AND / OR logic
Evaluate text, numbers, dates, and booleans
Stop a Repeater loop when a condition fails
Reference dynamic fields from upstream nodes
Stack up to 50 groups with 50 conditions each

Prerequisites

What you'll need before adding a Filter

An existing workflow in Konnectify with at least one upstream node that produces data.
Knowledge of the field names and value types (text, number, date, boolean) you want to evaluate.
For Repeater integration: the Filter node must be placed inside a Repeater node.

Understanding Filter Rules & Logic

Every Filter is built from groups of conditions. Understanding how they interact is key to building accurate rules.

Match type within a group

Match Type	Behavior
ALL	Every condition in the group must be true (logical AND)
ANY	At least one condition in the group must be true (logical OR)

Operator between groups

Operator	Behavior
AND	Both groups must pass
OR	At least one group must pass

Validation rule: Every condition must have a field and a comparison value (unless the operator doesn't require one). The workflow cannot continue until validation passes.

Key Components

Filter Groups CONTAINER

Groups are the top-level containers for conditions. Each group has its own ALL / ANY match type. Up to 50 groups per Filter node; the last group cannot be deleted.

Conditions RULE

Each condition has three parts:

Field — the data field to evaluate. Supports literal text or dynamic references using {{nodeId:fieldName}}.
Operator — the comparison logic (text, number, date, boolean, or generic).
Value — the comparison target. Hidden when the operator doesn't require one.

Operators Reference 5 CATEGORIES

Boolean — no value required

Operator	Description
Is true	Field value is true
Is false	Field value is false

Generic — no value required

Operator	Description
Exists	Field is present and not null/undefined
Does not exist	Field is absent, null, or undefined

Text — value required

Operator	Description
Contains	Field contains the value as a substring
Does not contain	Field does not contain the value
Starts with	Field starts with the value
Does not start with	Field does not start with the value
Ends with	Field ends with the value
Does not end with	Field does not end with the value
Exactly matches	Field equals the value exactly
Does not exactly match	Field does not equal the value

Number — value required

Operator	Description
Is equals to	Field equals the value
Is not equals to	Field does not equal the value
Is greater than	Field is greater than the value
Is lesser than	Field is less than the value
Is greater than or equal to	Field is ≥ the value
Is lesser than or equal to	Field is ≤ the value

Date — value required

Operator	Description
Before	Field date is before the value date
After	Field date is after the value date

Repeater Integration SPECIAL OPTION

When a Filter node is placed inside a Repeater, an extra option appears: "Stop the loop, if Filter fails".

Enabled: The entire Repeater loop stops immediately if the filter fails.
Disabled (default): The failed iteration is skipped; the loop continues to the next item.

When to Use

Use a Filter node when you need to control whether a workflow should proceed based on the data it is processing.

✓ Good fits

Only process records that meet specific criteria
Stop a loop early when a sentinel value is found
Route workflows based on field values
Validate required fields before downstream steps
Apply different logic for different statuses

✗ Not the right tool

Transforming(code block)
Branching into parallel paths (Branch/Path rule)
Iterating over a list (Repeater)
Introducing delays (Delay)

Step-by-step Guide

Add a Filter node

Open your workflow on the canvas.
Click the + button on any existing node.
Select Filter from the node type menu.
The sidebar opens automatically.

Set the group match type

Choose ALL (every condition must pass) or ANY (at least one must pass) for the first group.

Configure your conditions

Field: Select a field or type a literal value.
Operator: Pick from the dropdown (grouped by type).
Value: Enter a comparison value (hidden when not required).
Click + Condition to add more.

Tip: Conditions after the first show a logic label (AND for ALL groups, OR for ANY groups).

Add more groups (optional)

Click + Filter to add another group.
Toggle AND or OR between groups.
Set match type independently for each group.

Configure Repeater option (if applicable)

If inside a Repeater, decide whether to check "Stop the loop, if Filter fails".
Enabled = halt loop on first failure. Disabled = skip and continue.

Save and validate

Click Continue to save.
Resolve any red validation errors on invalid fields.
Once saved, the Filter node is active in your workflow.

Things to Know

Scenario	Behavior
No-value operator selected	Value field hidden; only field and operator shown
Single condition in a group	No logic label displayed; condition stands alone
Switching to no-value operator	Value hidden
Empty group	Shows "No conditions yet" placeholder
Deleting only condition	Delete button hidden — minimum 1 per group
Deleting only group	Delete button hidden — minimum 1 group required
Read-only mode	All inputs, buttons, and toggles are disabled

Limits at a glance

Restriction	Limit
Max filter groups per node	50
Max conditions per group	50
Minimum groups	1
Minimum conditions per group	1
Group operators	AND / OR
Match types	ALL / ANY

Important: Field references must point to valid upstream nodes. Broken references are flagged visually. Always verify upstream nodes are connected before testing.

Examples

Only process urgent, open Freshdesk tickets

Support ops · Freshdesk trigger · Slack notification

FRESHDESK

Only send a Slack alert when a ticket is both urgent and still open.

Group 1 · Match: ALL

priorityExactly matchesurgent

AND

statusExactly matchesopen

✓ Pass — Priority is urgent and status is open. Slack alert fires.

✗ Fail — Priority is normal or status is pending. No message sent.

Skip spam or bot-submitted forms

Lead capture · Web form trigger · CRM sync

GENERIC

Stop the workflow when a spam signal or filled honeypot field website_url is detected.

Group 1 · Match: ANY

emailContainsspam@

website_urlExists

✓ Spam — Either signal detected. Workflow halts.

✓ Legit — Clean email, empty honeypot. Continues normally.

Route high-value orders for manual review

E-commerce · Order trigger · Slack + task creation

E-COMMERCE

Trigger review only when order exceeds $5,000 and payment is verified.

Group 1 · Match: ALL

order_totalIs greater than5000

AND

payment_verifiedIs true

✓ Pass — $6,400, payment verified. Task and Slack alert fire.

✗ Fail — $320 or unverified payment. Normal fulfillment continues.

Escalate overdue tasks for VIP clients

Project management · Task update trigger · Multi-group

MULTI-GROUP

Page the account lead when a task is overdue AND the client is VIP.

Group 1 · Match: ANY (task at risk)

due_dateBefore{{today}}

task_statusExactly matchesblocked

AND

Group 2 · Match: ANY (client VIP)

client_tierExactly matchesenterprise

contract_valueIs greater than50000

✓ Pass — Task overdue AND client is enterprise. Lead paged.

✗ Fail — Task blocked but client is a startup. No page sent.

Workflow Diagrams

Pattern 1 — Simple gate

Trigger → Filter → pass Action | fail → stop

Pattern 2 — Filter inside a Repeater

Repeater loop

Filter → pass Action per item | fail → skip or stop

Pattern 3 — Chained filters

Trigger → Filter 1 → Filter 2 → Action

Testing Your Filter

Run a test with known data

Use the Test button on your trigger node to pull a real sample. The Filter shows pass or fail for that record.

Test the failing path too

Use a record that should not pass — confirm the workflow stops and downstream actions don't fire.

Check field reference pills

If a pill turns red, the upstream node is disconnected — fix the connection before testing.

Validate before you activate

Click Continue and resolve red errors. The workflow cannot be saved with incomplete conditions.

Good practice: Test with at least one passing and one failing record before activating. This catches logic errors like accidentally using ANY instead of ALL.

Frequently Asked Questions

Logic & Conditions

What is the difference between ALL and ANY inside a group?+

ALL means every condition must be true. If one fails, the group fails.

ANY means at least one must be true. The group passes on the first match.

Use ALL to narrow records; ANY to catch a broader set.

What is the difference between AND and OR between groups?+

AND: every group must pass. OR: at least one group must pass.

You can mix match types — one group ALL, another ANY.

Can I use a field from an upstream node as the comparison value?+

Yes. Both Field and Value inputs support dynamic references using {{nodeId:fieldName}}.

If a referenced node is disconnected, the pill turns red and saving is blocked.

What happens if a field doesn't exist in the incoming data?+

Exists fails. Does not exist passes. All other operators evaluate to false.

Add an Exists check as the first condition in an ALL group to handle this gracefully.

Are text comparisons case-sensitive?+

Yes. Urgent will not match urgent.

Normalise values in a Transform node before the Filter if casing is inconsistent.

Can I compare two numbers from different upstream nodes?+

Yes. Set Field to a reference from one node and Value to another node's reference.

If either is missing or non-numeric at runtime, the operator evaluates to false.

Groups & Structure

How many groups and conditions can I add?+

Up to 50 groups per Filter node and 50 conditions per group.

For more than 5–6 conditions per group, consider chaining Filter nodes.

Can I delete a group or condition?+

Yes, with one constraint: the last group and the last condition within a group cannot be deleted. The button hides automatically when only one item remains.

Can I collapse groups to reduce visual clutter?+

Yes. Each group has a chevron toggle that collapses the condition list while keeping the match type visible.

Is there a way to copy or duplicate a group?+

Not currently available. You'll need to recreate conditions manually in a new group.

Repeater & Workflow Behaviour

What happens when a filter fails — does it cause an error?+

No. A filter failure is a silent stop. No error, no retry, no downstream calls.

To act on failure, use a Branch/Router node instead.

What does "Stop the loop if Filter fails" do inside a Repeater?+

Disabled (default): Failed iteration skipped; loop continues.
Enabled: Entire loop halts on first failure.

Can I place a Filter node after another Filter node?+

Yes — chaining is supported. Data must pass all filters to reach downstream actions.

Does the Filter node modify data passing through it?+

No. It only evaluates. Use a Transform node to modify fields.

Validation & Troubleshooting

My filter isn't passing even though conditions look correct — what do I check?+

Casing — text operators are case-sensitive.
Field names — trailing spaces or wrong separators cause silent failure.
Data types — Number operator on a string returns unexpected results.
ALL vs ANY — confirm match type reflects your intent.
Broken references — a red pill means the upstream node is disconnected.
Test with a known record — use the Test button with real data.

Can I save a workflow with incomplete filter conditions?+

No. Saving is blocked until all conditions have a field and value (where required).

An incomplete condition would silently evaluate to false at runtime.

What does "read-only mode" mean on the Filter node?+

Applied when you lack edit permissions or the workflow is locked. All inputs and buttons are disabled.

Ensure you have the right permissions and the workflow is not currently executing to edit.

Ready to build smarter workflows?

Add a Filter node to your workflow and start controlling exactly when and how your automations run.

Get started free →