For the complete documentation index, see llms.txt. This page is also available as Markdown.

Filter

Filters give you control over your automation: they check data at specific points in the workflow and only let through what matches your criteria. That's how you build more targeted, intelligent flows.

What filters do

A filter is a checkpoint in your automation flow. It checks the data passing through against a condition — if the condition is met, the flow continues; if not, it stops there (or follows an alternative path).

Filter types

Filter
What it checks

Contains

Whether a specific value exists within a field — e.g. a keyword in a message.

Equal

Whether a value matches exactly — e.g. a customer ID.

Not Equal

Whether a value does not match — excludes specific data on purpose.

Greater Than / Less Than

Whether a value is above or below a given threshold.

Range

Whether a value falls within a defined range — e.g. a price range.

Is Not Empty

Whether a field is actually filled in.

And combination: "And" isn't a filter type on its own — it links multiple filters together. The flow only continues if all linked conditions are met. For example, you could combine "Contains 'urgent'" and "Equal Category: Support" for a more precise rule.

Examples in customer support

  • Prioritize urgent tickets: Filter by keywords like "urgent" or "critical" so these cases get handled first.

  • Route tickets to teams: Filter by category and automatically route to the right team.

  • Trigger follow-ups: Filter by customer response and automatically send a reminder email or notification.

Tip: Combine filters sparingly. The more conditions you chain together, the harder the flow becomes to follow later — document more complex filter chains directly in the automation's name or as a comment.

Last updated

Was this helpful?