Destination Node
Overview
Destination is the Workflow Builder step for choosing where output is sent. Before a data asset has been selected and saved, it is an unconfigured placeholder rather than a concrete runtime sink.
Workflow Builder fields
Configuration keys below are relative to the node configuration. Use the field name in the panel when following instructions in the builder; required markers such as an asterisk are not part of the name.
| Field in the panel | Configuration key | Where to edit / when shown |
|---|---|---|
| Asset Type | UI only; no separate config key | Choose a Data Asset; UI selection determines the sink type on Save |
| Asset Name | dataAssetId | Choose a Data Asset; reference to the selected data asset |
A new Destination with empty configuration is an unfinished choice of output, not an unknown connector or a failed runtime sink. Choose Asset Type, choose Asset Name (or Create New Asset), configure the fields for that type, then use the existing Save action. Saving assigns the concrete sink type and selected asset. Use the creation route offered for the selected asset type: Data Assets → Add New Data Asset in the main sidebar for types offered there, or Create New Asset in Destination when its catalog enables that type. Follow the linked connector guide for its creation and import requirements. Profiles and their credentials are managed separately in Settings → Connection Profiles.
Connector settings
The selected asset determines which settings appear in Configure Pipeline Settings. Endpoint, storage location, table or queue identity, and authentication are generally supplied by the asset and its connection profile; consult the specific connector page for exceptions.
The following table lists the complete Configure Pipeline Settings inputs for each generally available Destination type. Asset Type and Asset Name are common to all. For exact conditions and ownership, open the linked guide's Destination panel section; engine configuration and legacy-panel controls are separate surfaces.
| Destination family | Current pipeline settings | Configuration guide |
|---|---|---|
| S3 | Message Format, Batch Size, Flush Interval (ms); Parquet requires an asset Avro schema | Fields and ownership |
| Databricks | Batch Size; no Table Schema control | Fields and ownership |
| Databricks Zerobus | Payload Format, Enable Store and Forward; no Table Schema control | Fields and ownership |
| Amazon SQS | Batch Size; Message Group ID Expression and Deduplication ID Expression only for a FIFO asset | Fields and ownership |
| Splunk HEC | Source, Sourcetype, Batch Size, Verify SSL Certificates | Fields and ownership |
| Datadog Logs | Batch Size | Fields and ownership |
| Microsoft Sentinel | Batch Size, Time Generated Field | Fields and ownership |
| Snowflake | No additional pipeline settings | Fields and ownership |
| Apache Kafka / Amazon MSK | Payload Format, Additional Properties; no Partition Key Expression or Enable Store and Forward control | Fields and ownership |
The following Destination types are not generally available. Asset Type offers them only to accounts where they have been enabled:
| Destination family | Current pipeline settings | Configuration guide |
|---|---|---|
| Delta Lake (Asset Type: Databricks Delta Table) | Partition Columns, Additional Properties; no Table Schema control | Fields and ownership |
| Google Pub/Sub | Batch Size, Ordering Key Expression, Additional Properties | Fields and ownership |
| Elasticsearch | Batch Size | Fields and ownership |
| Palo Alto XSIAM | Batch Size | Fields and ownership |
| SignalFx | Payload Type; Metric Datapoints adds Metric Name Field, Value Field, Metric Type; Events adds Event Type Field; both use Timestamp Field, Batch Size | Fields and ownership |
Choosing the right panel instructions
Older workflows may open a connector-specific legacy panel. Its labels and editable values can differ from Destination, so use the legacy section of that connector guide when it matches the open editor.
If an asset is missing or cannot be loaded, restore or replace the asset reference before configuring connector settings. The absence of loaded asset details does not identify the connector as unsupported. After changing Asset Type or Asset Name, review the settings for the new selection and save it; instructions for the previous selection no longer describe the current panel.
See Data Assets and Connection Profiles for the settings owned outside the node.