Skip to content
Back to

Egress

Egress is how processed data leaves a workflow: download files from Save File Export, call external APIs with REST API or GraphQL API nodes, or sync to catalog destinations through Data Connector nodes. Server-side runs keep export files on your workspace storage until you download them from the node or the Files UI.

Downstream connector catalog

Section titled “Downstream connector catalog”

Egress mechanisms

Section titled “Egress mechanisms”
Data Export

Automatically upload transformed data to internal or downstream warehouses, lakes, BI, accounting, and domain platforms.

Mechanism Description
Save File Export CSV, TSV, PSV, XLS, JSON, XML, TXT, and FIX (.fix round-trip). You download the complete file from the node or the Files UI after a server run. Later runs keep that file available so you can download it again.
REST API node Call external HTTP APIs with persisted method, headers, query, body, and auth on the node; map responses into the workflow dataset.
GraphQL API node Execute GraphQL queries against external endpoints.
Data Connector (Airbyte) Catalog destinations (and sources) through the same PyAirbyte path as ingress.

Save File downloads

Section titled “Save File downloads”

After a server run, you download the complete export from the Save File node or the Files UI. The engine persists the file under that run. When the node does not need to re-export, the next run still keeps the file so download stays available. When you change the file name, format, or folder, the next run writes the new file and removes the previous file from the workspace.

On the Save File tab, Folder is the workspace folder tree for this namespace. You expand a folder and select where the file is written. The tree lists folders. The namespace system folder .fontana stays out of the tree.

FIX round-trip export

Section titled “FIX round-trip export”

Save File Export can write .fix files with SOH delimiters and recomputed checksum fields (BodyLength, CheckSum). The canvas preview uses pipe delimiters for readability. Export requires mappable columns plus BeginString and MsgType on each row. See Supported formats for FIX import behaviour.

Connector and API secrets

Section titled “Connector and API secrets”

Outbound connectors and API nodes use the same Vault-backed secret model as ingress. Values resolve when a run executes; nothing sensitive is embedded in workflow config. See Data for the secrets model.

Section titled “Related documentation”