Export Node
Export automation records to a downloadable file
Last updated 8 Oct 2026
The Export node serializes its input records to a file (CSV, JSON, or GeoJSON), uploads it to file storage, and exposes a signed download URL. It passes the input records through unchanged, so it can sit anywhere in an automation rather than only at the end.
When to Use
Use Export when you want a downloadable artifact of the data at a point in the automation — the enriched dataset, a filtered subset, or a GeoJSON layer for mapping. To push records into an external system instead, use the Integration or HTTP node.
Configuration
| Field | Type | Description |
|---|---|---|
format | csv | json | geojson | Output file format (default: csv). Required |
filename | string | Output filename without extension (default: export) |
Example
Export the current records as CSV:
format: csv
filename: enriched_prospects
Notes
- The node passes its input records through unchanged on the
dataoutput. - The generated file is uploaded to storage and a signed download URL (valid for one hour) is recorded in the run metadata, alongside a short content preview.
- GeoJSON export builds a
FeatureCollectionfromlatitude/longitudecolumns; rows missing or with invalid coordinates are dropped and the count is logged as a validation warning. - If the storage upload fails, the export does not fail the run — the records still pass through and the content preview remains available.
Related articles
Still stuck? Browse the FAQ or contact us.