> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/filters/is-not-empty.md).

# Is Not Empty

### Overview

The **Is Not Empty Filter Component** checks whether a given input field contains data. If the field is not empty, the message is passed through the `notEmpty` port; otherwise, it is routed to `empty`.

### Usage

This component is used to validate whether a text, number, or boolean value is present before proceeding with further processing in workflows.

#### Properties

| Property     | Type  | Description                                     |
| ------------ | ----- | ----------------------------------------------- |
| `sourceData` | `any` | The data field to be checked for non-emptiness. |

#### Input Ports

| Port | Description                        |
| ---- | ---------------------------------- |
| `in` | Accepts input data for validation. |

#### Output Ports

| Port       | Description                                      |
| ---------- | ------------------------------------------------ |
| `notEmpty` | Emits the message if `sourceData` contains data. |
| `empty`    | Emits the message if `sourceData` is empty.      |

#### Processing Logic

1. **Receives Input Data**:
   * Accepts a dataset (`sourceData`) from the input.
2. **Checks for Non-Empty Condition**:
   * If `sourceData` is a number or boolean, it is considered **not empty**.
   * If `sourceData` is an empty string, array, object, or `null`, it is considered **empty**.
3. **Routes the Message**:
   * If `sourceData` contains data, the message is sent to the `notEmpty` port.
   * Otherwise, it is sent to the `empty` port.

#### Output Data Schema

| Property     | Type      | Description                                             |
| ------------ | --------- | ------------------------------------------------------- |
| `sourceData` | `any`     | The original data that was checked.                     |
| `result`     | `boolean` | `true` if `sourceData` is not empty, otherwise `false`. |

### Notes

* **Supports Various Data Types**: Works with text, numbers, booleans, arrays, and objects.
* **Automatically Handles Numbers & Booleans**: These values are never considered empty.
* **Ideal for Conditional Filtering**: Useful in workflows that need to check for data presence before proceeding.

This component is essential for workflows that require validation of data presence before further processing.


---

# 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.appmixer.com/connector-configuration/utils/filters/is-not-empty.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.