Egress
Write upstream records through a workspace destination endpoint
Egress sends the selected upstream records to an external destination. It resolves the endpoint’s installed writer and target, then applies the supported write mode and any resolved write policy. It is separate from source reads and ontology fact-store materialization.
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 |
|---|---|
Data endpoint / dataEndpointId | A destination endpoint backed by a write capability |
source | Selected upstream record output |
Write mode / writeMode | append, replace or upsert, only where implemented |
policy.write | A real approved write-policy reference when the path requires one |
Configure
Prepare the egress 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.Select Data endpoint and Write mode in the egress inspector. Connect its input to the actual upstream output. Inspect the endpoint’s schema/table/object path and installed write contract before running.
Put this section under egress on a full node of kind egress. It is not a standalone API or MCP request. Replace resource placeholders, and provide the full node ports/policy and graph edges.
{
"dataEndpointId": "<DESTINATION_ENDPOINT_UUID>",
"source": "orders",
"writeMode": "append"
}Verify a bounded run
For the dedicated two-row output table, inspect IDs 1 and 2 and their values using the external system as well as run diagnostics. A run count alone does not establish that the intended table/path received the data.
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
Append is not automatically upsert. Replacement can remove/recreate existing data. Transaction scope, key requirements, row-level security and partial-write behavior depend on the writer. Cancellation is not rollback.