Export Node

The Export Node saves workflow data as a downloadable file.

Supports multiple file formats and customizable output settings.

Purpose

Saving Results: Store the final output of data analysis or transformation.
Report Generation: Create structured reports (CSV, JSON, HTML, Markdown).
Data Sharing: Prepare data for use in other apps or sharing with others.
Archiving: Save snapshots of workflow data at key moments.

Configuration

Configurable properties:

Property	Type	Description	Default
label	string (optional)	Descriptive name for the node instance.	'Export'
exportFormat	'csv' \| 'json' \| 'txt' \| 'html' \| 'markdown'	File format for the export.	'csv'
fileName	string (optional)	Base name for the file (no extension).	'exported-data'
includeTimestamp	boolean (optional)	Append a timestamp to the file name for uniqueness.	true
flatten	boolean (optional)	For CSV, flatten nested JSON into columns.	true
customSeparator	string (optional)	For CSV, custom character to separate values.	','

Timestamp Generation

The node preview shows filenames like fileName_timestamp.ext. Timestamp format (e.g., YYYYMMDD_HHMMSS) is generated by backend logic.

Inputs and Outputs

Input (Left Handle):
Receives the data to export. The required structure depends on exportFormat (see details below).

Output (Right Handle, id: "output"):
Emits data after the export.
(Clarification recommended: is this the original data, a status, or a file link?)

Logic of Exportation

Data arrives at the input handle.
On execution (auto or button click):

Data is processed by exportFormat and options (flatten, customSeparator).
File is generated with fileName, optionally timestamped.
Browser prompts user to download the file.

Note: Large files may require backend processing.

Format-Specific Details

CSV:
- Input: Array of flat JSON objects. Each object = row.
- flatten: If true, nested JSON becomes columns (e.g. user.name).
- customSeparator: Defines the column delimiter.
JSON:
- Input: JSON object or array.
- Output: Pretty-printed JSON.stringify.
TXT:
- Input: Any data.
- Output: Stringified representation (objects/arrays via JSON.stringify).
HTML/Markdown:
- Input: (Clarification needed) Structured data (auto-table?) or pre-formatted string?
- Output: HTML/Markdown file.

HTML & Markdown Data Transformation

Document input structure and conversion logic for HTML/Markdown exports to avoid surprises for users.

Example: Exporting Processed Orders to CSV

Input Data Example:

[
{ "orderId": "ORD001", "customerName": "Alice Smith", "totalAmount": 150.75, "status": "Shipped" },
{ "orderId": "ORD002", "customerName": "Bob Johnson", "totalAmount": 89.99, "status": "Processing" }
]

Node Configuration:

label: Export Shipped Orders
exportFormat: csv
fileName: shipped_orders_report
includeTimestamp: true
flatten: true
customSeparator: ','

Resulting CSV file:

orderId,customerName,totalAmount,status
ORD001,Alice Smith,150.75,Shipped
ORD002,Bob Johnson,89.99,Processing

Notes and Considerations

User Interaction: Manual and/or automatic export, depending on node config.
File Size Limitations: Large files may require backend support.
Browser Pop-up Blockers: Ensure downloads are not blocked by pop-up settings.
Error States: Export errors are reported in the node UI.

The Export Node is the bridge for moving your workflow data into files for use anywhere.