> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/export-to.md).

# Export To

## Enable Data Export from Your Data Table

{% hint style="info" %}
This interaction is only available when using the [Avonni Data Table](/flow/flow-components/data-table.md).
{% endhint %}

The Avonni Data Table lets users export their data to an Excel or CSV file. This is helpful for analyzing, sharing, or archiving data outside of Salesforce.

<figure><img src="/files/OpoVvr74chZd38hSfSFb" alt=""><figcaption></figcaption></figure>

## Steps to Create an "Export to" Interaction

### 1️⃣ Add an Action Button

Decide whether you want the export button to be a [**row action**](/flow/tutorials/components/data-table/creating-row-actions.md) (on each row) or a [**header action**](/flow/flow-components/data-table.md#header) (at the top of the table).

{% @arcade/embed url="<https://app.arcade.software/share/koTSHldm1QynABdHFPnM>" flowId="koTSHldm1QynABdHFPnM" %}

### 2️⃣ Create the interaction:

<figure><img src="/files/AYNBTYyHSMOf4Umn7e5H" alt=""><figcaption></figcaption></figure>

* In the "Interactions" tab, click "Add" and choose "Row Action Interaction" or "Header Action Interaction," depending on what you chose in step 1.
* Select the name of the action you created.
* Choose "**Export To**" as the interaction type.
* Enter a default file name for the exported file (users can change this later).
* (Optional) If you want to simplify the process, you can hide the export dialog. This prevents users from choosing the file format and encoding.
* Select the file format(s) you want to allow (Excel, CSV, or both).
* Choose the default encoding for the file.

**That's it!** Now your users can easily export data from the Data Table.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/export-to.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.