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

# Export CSV

**Description**: The **ExportCSV** component exports structured data into a CSV file.

### Input Parameters

| Parameter     | Type      | Required | Description                                                      |
| ------------- | --------- | -------- | ---------------------------------------------------------------- |
| `data`        | `array`   | ✅        | The structured data to be converted into CSV format.             |
| `fileName`    | `string`  | ✅        | The name of the output CSV file, including the `.csv` extension. |
| `withHeaders` | `boolean` | ✅        | Set to `true` if the first row should contain column headers.    |

### Output Parameters

| Parameter  | Type     | Description                        |
| ---------- | -------- | ---------------------------------- |
| `fileId`   | `string` | The ID of the generated CSV file.  |
| `fileName` | `string` | The name of the exported CSV file. |

### Instructions

1. **Define Data Source**:
   * Provide structured data in an array format, ensuring proper key-value mapping.
2. **Set Output File Name**:
   * Choose a name for the CSV file, including the `.csv` extension.
3. **Include Headers (Optional)**:
   * Enable **Use Headers** if the first row should contain column headers.
4. **Processing**:
   * The component processes the structured data and creates a CSV file.
   * The newly generated file is output with its `fileId` and `fileName`.

***


---

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