> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/automation/workflows/filter.md).

# 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.

<figure><img src="/files/OJwWBPH0M1EsHB4swQaC" alt=""><figcaption></figcaption></figure>

### 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&#x20;

| 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/equipme/automation/workflows/filter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.