# Identity

### Overview

The **Identity Filter Component** allows messages to pass through unchanged. It acts as a transparent relay, forwarding incoming data to the output without modification.

### Usage

This component is used in workflows where an incoming message needs to be relayed without transformation, ensuring seamless message propagation.

#### Input Ports

| Port | Description                   |
| ---- | ----------------------------- |
| `in` | Accepts the incoming message. |

#### Output Ports

| Port  | Description                                       |
| ----- | ------------------------------------------------- |
| `out` | Emits the same message received at the `in` port. |

#### Processing Logic

1. **Receives Input Data**:
   * Accepts any incoming message at the `in` port.
2. **Forwards Data Unchanged**:
   * Passes the received content directly to the `out` port without any processing or filtering.
3. **Maintains Message Integrity**:
   * Ensures that message type and encoding remain intact.

#### Output Data Schema

| Property          | Type     | Description                                                               |
| ----------------- | -------- | ------------------------------------------------------------------------- |
| `content`         | `any`    | The original message content, unchanged.                                  |
| `contentType`     | `string` | The type of the message content (e.g., `application/json`, `text/plain`). |
| `contentEncoding` | `string` | The encoding format of the message content.                               |

### Notes

* **Transparent Message Relay**: Forwards messages exactly as received.
* **No Filtering or Transformation**: Ensures data integrity.
* **Ideal for Debugging & Workflow Testing**: Helps verify message flow within a pipeline.

This component is essential for workflows where messages need to be relayed unchanged while maintaining their structure and metadata.


---

# Agent Instructions: 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:

```
GET https://docs.appmixer.com/connector-configuration/utils/filters/identity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.