# Remove

### Overview

The **Remove Storage Component** deletes a specified key-value pair from storage, ensuring the removal of outdated or unnecessary data.

### Usage

This component is used to remove a specific item from a storage location using a given key.

#### Input Ports

| Port | Description                              |
| ---- | ---------------------------------------- |
| `in` | Receives the key to remove from storage. |

#### Output Ports

| Port      | Description                                                         |
| --------- | ------------------------------------------------------------------- |
| `removed` | Emits details of the removed item, including its key and old value. |

#### Properties

| Property  | Type     | Description                                                 |
| --------- | -------- | ----------------------------------------------------------- |
| `storeId` | `string` | The ID of the storage space where the item will be removed. |

#### Processing Logic

1. **Receives Key**: Accepts a key identifying the item to remove.
2. **Removes from Storage**: Deletes the key-value pair from the specified `storeId`.
3. **Returns Confirmation**:
   * If the key exists, outputs the removed key and its old value.
   * If the key does not exist, the component does not output any data.

#### Output Data Schema

| Property   | Type     | Description                             |
| ---------- | -------- | --------------------------------------- |
| `key`      | `string` | The key of the removed item.            |
| `oldValue` | `string` | The previous value of the removed item. |

### Notes

* **Selective Deletion**: Ensures only specified keys are removed.
* **Efficient Storage Management**: Helps maintain clean and optimized storage.
* **Supports Automation**: Useful for workflows where data needs to be dynamically deleted.

This component is ideal for workflows that require selective removal of stored data based on specific keys.


---

# 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/remove.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.