Excel Export Stage
The Excel Export stage generates an .xlsx spreadsheet with the data prepared in the flow—each connected source becomes a sheet in the spreadsheet. Use it when the results need to be consumed in a spreadsheet: for reconciliations, operational reports, or sharing with teams that work in Excel. Excel Export is in the Analysis and Export category on the toolbar and is available in Turbo AI processes.
How to configure
Connect the sources whose data should be exported to the stage, then configure:
Name: identifies the stage in the flow (up to 100 characters).
File name pattern: defines the name of the file generated each time the process runs. It accepts dynamic variables—for example,
export_{referenceDate:yyyyMMdd}generates a file with the reference date in its name. The available variables are {referenceDate} (reference date), {timestamp} (run date and time), {id} (unique run identifier), {code} and {name} (process code and name), {folder} and {folderName} (code and name of the run folder).Sheets: each connected source becomes a sheet in the spreadsheet. For each one, set the Sheet name (required and unique) and its display Order.
Excel limits are handled automatically: Excel supports up to 1,048,575 rows of data per sheet. When a source exceeds this limit, the stage splits the data into additional numbered sheets—nothing is lost.
Where the file goes
Without additional configuration, the file is stored in the platform's internal storage, where it is available to Download or View in the run's export panel. To automatically deliver it to an external destination (e.g., an SFTP server or an Amazon S3 bucket), configure the Output Directory in the process settings.
Usage example
A card reconciliation process generates two results: reconciled items and outstanding items. Both sources are connected to the Excel Export stage, with the sheets named "Reconciled" and "Outstanding" and the file name pattern conciliacao_cartoes_{referenceDate:yyyyMMdd}. Each time the process runs, the operations team receives a single spreadsheet, with that day's results separated into sheets.
Best practices
Use variables in the file name ({referenceDate}, {timestamp}) to keep a history and avoid overwriting files between runs.
Very large volumes can make spreadsheets cumbersome to open—above a few hundred thousand rows, consider Text File Export, Database Export, or the Data Lake.
Related articles
Text File Export Stage
Document Export Stage
Database Export Stage
File repositories: which ones Dattos connects to and how to set them up