Asset
Stage an intermediate data artifact and optionally persist it through an endpoint
An Asset node stages a supported upstream connector/operator result as a data artifact so downstream work can refer to an inspectable handle. It is executable through a special asset path even though it has no default tool name. A persisted asset destination requires an appropriate installed writer endpoint.
Before using it
Create or select the real resources described above in the pipeline’s project/workspace, inspect the upstream data shape and ensure your actor can perform this operation. A configuration fragment cannot create those resources. Read First pipeline for a complete graph and fixture.
Fields and bindings
| Field | Meaning |
|---|---|
assetName | Name for the staged artifact |
source / output | Upstream and resulting data-pool names |
stage | raw, clean, enriched, semantic or analytics |
dataEndpointId | Optional endpoint used for configured persistence |
mapping | Optional output columns and mapping rules |
storage.writeMode | append, replace or upsert where the target supports it |
Configure
Prepare the asset node for the selected test resources. Use the operation and fields shown in this example. Show actual resource bindings, upstream/downstream ports and any write/model effects before applying the draft.Connect ingress to the Asset node input, choose an artifact name/stage and inspect any output mapping or persistence settings. A friendly stage label does not clean or enrich records by itself.
Put this section under asset on a full node of kind asset. It is not a standalone API or MCP request. Replace resource placeholders, and provide the full node ports/policy and graph edges.
{
"assetName": "demo_orders_raw",
"source": "orders",
"output": "staged_orders",
"stage": "raw"
}Verify a bounded run
Inspect the resulting handle/artifact, columns and two known record IDs. If persistence is configured, inspect the external target separately and verify its write count/receipt.
Validate, save a version and run a small known fixture. Inspect the actual node result and downstream consumer, not only the graph preview.
Limits and failure behavior
The asset path requires a supported upstream operator/asset data handle. A source-less Asset node cannot manufacture rows. Naming a stage is not a transform; external writes still depend on endpoint permissions and connector guarantees.