# On Item Removed

### Overview

The **On Item Removed Component** triggers when an item is removed from storage, providing real-time updates whenever a deletion occurs.

### Usage

This component is used to monitor a specified storage location and trigger workflows whenever an item is deleted.

#### Output Ports

| Port   | Description                                    |
| ------ | ---------------------------------------------- |
| `item` | Emits the details of the removed storage item. |

#### Properties

| Property  | Type     | Description                                  |
| --------- | -------- | -------------------------------------------- |
| `storeId` | `string` | The ID of the storage space being monitored. |

#### Processing Logic

1. **Registers Webhook**: The component registers a webhook to listen for storage item deletions.
2. **Monitors Deletions**: Whenever an item is removed, the webhook captures its details.
3. **Sends Data**:
   * If a deletion occurs, the component outputs the item's details to `item`.
   * The webhook ensures that only deletions are processed.

#### Output Data Schema

| Property    | Type     | Description                                   |
| ----------- | -------- | --------------------------------------------- |
| `key`       | `string` | The key of the removed item.                  |
| `value`     | `string` | The value of the removed item.                |
| `storeId`   | `string` | The storage ID where the item was removed.    |
| `createdAt` | `string` | The timestamp when the item was created.      |
| `updatedAt` | `string` | The timestamp when the item was last updated. |

### Notes

* **Real-Time Monitoring**: Captures deletions as they happen.
* **Webhook-Based Execution**: Efficiently listens for storage updates.
* **Supports Automation**: Ideal for triggering workflows when data is removed.

This component is essential for workflows that require automatic processing of deleted storage entries in real time.


---

# 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/storage/on-item-removed.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.