Data Export
Turns any table your agent produced into an Excel or CSV file, attached to the reply and ready to download.
We start with What Data Export does, move on to How to ask for a file, cover Large results, and wrap up with Permissions.
What Data Export does
Data Export turns a table into an Excel (.xlsx) or CSV file and attaches it to the agent's reply, so you can download it and carry on working in a spreadsheet.
It is not tied to one source. Anything your agent can produce as rows can become a file: a database query, an order list, leads, products, an ads or analytics report. The skill that fetched the data and the skill that writes the file are separate, which is what makes "pull it from there, give it to me as Excel" work without a special integration for each source.
There is nothing to configure. Install it on the agent and ask.
How to ask for a file
Just say what you want and add that you want it as a file:
- "pull the cancelled orders from last month and send them to me as Excel"
- "give me the customer list as a spreadsheet"
- "export this as CSV"
The agent produces the table, hands it to Data Export and the file appears in the reply. It also tells you what is in the file and how many rows it has, so you can tell at a glance whether the answer looks right before opening it.
Large results
There are two ways rows reach the file, and the size decides which one is used.
Ordinary results travel through the conversation: the agent holds the rows and hands them over. This works from any source, with no extra setup, up to a couple of thousand rows.
Big exports are handed over by reference instead: the skill that produced the data writes the full result to a file and Data Export reads it from there, so the rows never pass through the chat. That is why "export 50,000 rows" works and costs roughly what a short answer costs. Files are written up to 100,000 rows; beyond that, narrow the request (a date range, fewer columns) and the agent will tell you it was cut.
The handover has to be supported by the source. The Database skill supports it today; other sources use the ordinary path, so a very large export from them is capped rather than complete.
Permissions
Exporting is its own permission. Reading data and taking all of it out as a downloadable file are different decisions, so a workspace can allow the first without the second.
If your workspace uses custom roles, grant the Data Export capability in Roles & Access to the roles that should be able to produce files.