tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Workflow Filter Conditions: Stop Unwanted Runs Early

FlowMattic Filter module: a WooCommerce order passes a Continue If condition on the order total before a Slack alert is sent.

Workflow filter conditions decide whether a run is worth finishing. In FlowMattic, the Filter module checks data from the trigger or any earlier step against conditions you set, then either lets the run continue or ends it on the spot, so the steps after it never fire for events you don’t care about.

It is the module to reach for when a trigger fires more often than it should: test orders, forms from existing customers, webhooks for event types you don’t handle. One Filter step near the top of a workflow keeps your CRM, your Slack channels and your inbox free of noise.

What is the Filter module?

The Filter is a built-in step called Filter by FlowMattic. You find it in the app picker under Flow Controls, described as “Continue only when your conditions are met.” It has two action events:

  • Continue If Condition Meet: the run carries on only when your conditions match. Otherwise it stops at the Filter.
  • Exit If Condition Meet: the run stops when your conditions match. Otherwise it carries on.

The two are mirror images. Pick whichever reads more naturally for the rule you have in mind: “continue if the order total is over 500” or “exit if the email ends with a test domain”. Both live alongside the other workflow logic modules on the same canvas as your app steps.

How workflow filter conditions work

  1. In the visual builder, add a step after your trigger (or after any step whose data you want to check) and choose Filter by FlowMattic.
  2. On the Setup tab, pick the action event: Continue If Condition Meet or Exit If Condition Meet.
  3. On the Configure tab, build your Filter Conditions. Each condition has three parts: Choose field (a dynamic tag from an earlier step), Choose condition (the comparison) and Enter or select value.
  4. Click AND to add another condition to the same group, or OR to start a new group.
  5. Open the Test tab to check the result against your sample data.

The grouping logic behind workflow filter conditions is simple: every condition inside a group must match for that group to pass, and the Filter passes when any one group passes. So “country is US AND total over 100” OR “customer tag is VIP” is two groups, the first with two conditions.

FlowMattic Filter step Configure tab with a Greater than (Number) condition on the order total.
A Filter step set to Continue If Condition Meet, letting the run through only when the order total is greater than 500.

At run time, a passing Continue If step lets the run move on to the next step. When it does not pass, it records “Conditions does not meet. Execution will stop.” and nothing after it runs. Exit If works the other way round. Either way, Task History keeps the conditions the Filter checked.

Every condition the Filter offers

The condition list holds 32 comparisons, grouped by the kind of value they expect. Conditions that need no value (such as Exists or Is Valid JSON) hide the value box.

TypeConditions
TextContains, Does not contain, Exactly matches, Does not exactly match, Is in, Is not in, Starts with, Does not start with, Ends with, Does not end with
NumberGreater than, Less than, Equal to, Not equal to, Greater than or equal to, Less than or equal to
Date/timeAfter, Before, Equals, Does not equal
BooleanIs true, Is false
PresenceExists, Does not exist, Is empty, Is not empty, Is blank, Is not blank
Format checksIs Valid Email Format, Is Valid JSON, Is Valid URL Format, Is Numeric

Is true matches true or 1. Is false matches false, 0 or an empty value. The value box accepts dynamic tags, so you can compare two fields from the run.

Use cases

Keep test orders out of your fulfilment flow

Staff place test orders, and they should never reach the warehouse sheet. An Exit If step on the order note stops them before anything else runs.

WooCommerce new order → Filter (Exit If: customer note Contains "test") → Google Sheets row → Slack message

Alert sales only about high-value orders

A Slack ping for every order becomes noise. Filter on the total so the channel only lights up when it matters.

WooCommerce new order → Filter (Continue If: total Greater than 500) → Slack message to #big-orders

Qualify agency leads before they reach the CRM

An agency’s contact form collects a budget field. Two conditions in one group make sure only real, qualified leads are created as contacts.

Fluent Forms submission → Filter (Continue If: email Is Valid Email Format AND budget Greater than or equal to 2000) → HubSpot contact

Handle only the webhook events you care about

A SaaS billing provider sends many event types to one webhook URL. Match the event name exactly and let everything else stop quietly.

Webhook (Capture Webhook Response) → Filter (Continue If: type Exactly matches invoice.payment_failed) → Send Email to the customer

Escalate urgent support tickets

Use two OR groups so either an urgent priority or the word “outage” in the subject reaches the on-call channel.

Freshdesk new ticket → Filter (Continue If: priority Exactly matches urgent OR subject Contains outage) → Slack message to #on-call

Act only on what an AI agent classified as a lead

An AI Agent reads each inbound message and answers with one word. The Filter turns that answer into a hard gate before anything is written to your CRM.

Webhook → AI Agent (classify as sales, support or spam) → Filter (Continue If: answer Exactly matches sales) → FluentCRM contact

Tips and gotchas

  • Text comparisons ignore case. Both the field and the value are lowercased before comparing, so “Acme” Exactly matches “acme”.
  • Number conditions compare whole numbers. The decimal part is dropped before comparing, so 50.75 counts as 50 and is not Greater than 50. If cents matter, scale the value first, for example with the Maths module.
  • Is in checks text inside your list. It passes when the field’s value appears anywhere in the comma-separated list you typed, so a short value such as us also matches a list containing aus. When values overlap, use Exactly matches in separate OR groups.
  • Is empty and Is blank differ. Is blank is true only for an empty value. Is empty is also true for 0 and for an empty list [].
  • Dates must parse. Date/time conditions read both sides as dates. If either side can’t be read as a date, the condition does not match.
  • An empty Continue If stops. A Continue If step with no conditions has nothing to match, so the run stops there.
  • Inside an Iterator, a stop skips one item. When a Filter inside a loop stops, the remaining steps for that item are skipped and the loop moves on to the next item.

You don’t always need a Filter step. Every action step has a Conditions tab with Enable Conditional Execution, which skips just that one step when its conditions don’t match. The trigger’s Conditions tab can stop the whole workflow before step one, and it is also where Skip Duplicate Events lives. Use a Filter when you want the decision visible as its own step in the middle of the chain.

Related features

  • Router: when an event needs different handling instead of a yes or no, split it into named routes.
  • Branch: the same conditions, but the No side gets its own steps instead of ending the run.
  • Workflow error handling: when a failed check should mark the run as Failed and alert you, use Stop and Error instead of a Filter.

FAQ

What is the difference between a Filter and a Router?

A Filter makes one decision: keep going or stop. A Router splits the run into several named routes, each with its own conditions and its own steps. Use a Filter to drop unwanted events, and a Router when different events need different actions.

Are filter conditions case-sensitive?

No. FlowMattic lowercases both the field and the value before comparing text, so capitalisation never decides the result. That applies to Contains, Exactly matches, Starts with and the other text conditions.

Can I see why a run was filtered out?

Yes. Open the run in Task History and expand the Filter step. It shows the conditions it checked and the message it recorded, such as “Conditions does not meet. Execution will stop.”

Workflow filter conditions are included in every FlowMattic plan, with unlimited workflows and runs on your own server. Compare plans on the pricing page and add your first Filter today.

More from the blog