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”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). Download from the node or the Files UI after a server run. |
| REST API node | Call external HTTP APIs; 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. |
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.
Related documentation
Section titled “Related documentation”- Ingress - upstream sources and PyAirbyte execution
- Storage and processing - secure workspace storage for export files
- Workflow orchestration - canvas execution model