> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/workflows/nodes/logic/condition.md).

# Filter

The **Filter Node** acts as a smart filter within your workflow, letting you control which records should proceed to the next step based on custom logic and property values.

With this node, you can add logic like:\
\&#xNAN;*"Only continue if Company Country is US."*

***

### When to Use It

Use the Filter node when you want to:

* Run different automations for different segments (e.g., US vs. non-US accounts)
* Filter out records that don’t meet your criteria before taking an action (like syncing, enrolling, or enriching)
* Build branching, multi-path workflows based on any field or attribute

***

### Configuration Overview

Here’s how the Filter Node works:

The **Filter Node** allows you to apply conditional logic to control which records continue in your workflow. You can filter by account or contact properties, including both standard and AI-enriched fields.

#### Configuration Options

1. **Filter Type**
   * **If** → Define a condition that must be true for records to continue.
   * **Else** → Define a fallback path for records that do not meet the condition.

     <figure><img src="/files/TuCDQ7NjtdexrEUHsxo6" alt=""><figcaption></figcaption></figure>
2. **Filter Scope**
   * **Account** → Apply conditions on account-level properties.
   * **Contact** → Apply conditions on individual contact-level properties.
3. **Define Conditions**
   * **Select a Property** → Choose the account or contact property you want to filter on.
   * **Choose an Operator** → Options include `is`, `is not`, `contains`, `greater than`, `less than`, etc.
   * **Set a Value** → Enter the value or criteria that must be matched for records to pass through.

#### Example

* Filter:
  * **Company Country is US**
* Workflow Behavior:
  * ✅ Records with **Company Country = US** will continue through this path.
  * ❌ Records from other countries will be excluded (or follow the Else path if defined).

***

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


---

# 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://docs.hockeystack.com/account-intelligence/workflows/nodes/logic/condition.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.