> 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/not-equal.md).

# Not Equal

### Overview

The **Not Equal Filter Component** checks whether a given input data is not equal to a specified value. If the condition is met, the message is passed through the `notEquals` port; otherwise, it is routed to `equals`.

### Usage

This component is used to validate if a text, number, or date is different from a predefined value, making it useful for conditional processing in workflows.

#### Properties

| Property     | Type     | Description                                                |
| ------------ | -------- | ---------------------------------------------------------- |
| `sourceData` | `string` | The data to be compared. Can be a string, number, or date. |
| `value`      | `string` | The value to compare against `sourceData`.                 |

#### Input Ports

| Port | Description                                          |
| ---- | ---------------------------------------------------- |
| `in` | Accepts input data and the value to compare against. |

#### Output Ports

| Port        | Description                                                |
| ----------- | ---------------------------------------------------------- |
| `notEquals` | Emits the message if `sourceData` is not equal to `value`. |
| `equals`    | Emits the message if `sourceData` is equal to `value`.     |

#### Processing Logic

1. **Receives Input Data**:
   * Accepts a dataset (`sourceData`) and a comparison value (`value`).
2. **Checks for Non-Equality**:
   * Performs a comparison (`sourceData != value`).
3. **Routes the Message**:
   * If `sourceData` is not equal to `value`, the message is passed to the `notEquals` port.
   * If `sourceData` is equal to `value`, it is passed to the `equals` port.

#### Output Data Schema

| Property     | Type      | Description                                                        |
| ------------ | --------- | ------------------------------------------------------------------ |
| `sourceData` | `string`  | The original data that was checked.                                |
| `value`      | `string`  | The value compared against `sourceData`.                           |
| `result`     | `boolean` | `true` if `sourceData` is not equal to `value`, otherwise `false`. |

### Notes

* **Strict Comparison**: Ensures only different values pass through.
* **Supports Various Data Types**: Works with text, numbers, and dates.
* **Ideal for Conditional Filtering**: Useful in workflows requiring validation that two values are not the same.

This component is essential for workflows that need to filter or route messages based on whether a value differs from a predefined value.


---

# 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/not-equal.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.