> 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/csv/deletecolumns.md).

# Delete Columns

### Overview

The **DeleteColumns** component removes specific columns from a CSV file. It allows users to define which columns to delete, using either column names (if headers exist) or column indices.

### Usage

#### Input Parameters

| Parameter     | Type      | Required | Description                                                                                                 |
| ------------- | --------- | -------- | ----------------------------------------------------------------------------------------------------------- |
| `withHeaders` | `boolean` | ✅        | Set to `true` if the first row represents column names (CSV header) and should be used to identify columns. |

#### Output Parameters

| Parameter | Type     | Description                       |
| --------- | -------- | --------------------------------- |
| `fileId`  | `string` | The ID of the processed CSV file. |

### Instructions

1. **Determine Column Identification Method**
   * If the first row contains column names, set `withHeaders` to `true`. This ensures the correct columns are deleted based on their names.
   * If column names are not available, columns are identified by index.
2. **Select Columns to Remove**
   * Specify the columns you want to delete.
   * Ensure the correct format is used for column identification.
3. **Processing**
   * The component removes the selected columns and generates a new CSV file.
   * The modified file is returned with a new `fileId`.
4. **Output**
   * The processed file can be downloaded or used as input for further data 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/utils/csv/deletecolumns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.