Input node
Platform Input type. Every upload-driven session template starts with input-node. Ingest writes blobs to object storage, whether it arrives through the v2 API, HEAT Capture, the toolkit or HEAT Control Centre (formerly Cluster Manager). Each upload creates a new node output on the input node instance.
Configuration
| Property | Required | Description |
|---|---|---|
dataSourceName | No | Target store; defaults to HEAT Managed Object Store |
Instance naming
The graph name (Nodes[].Name in session templates) communicates expected payloads:
| Name | Use when |
|---|---|
agnostic-input | Capture protobuf, mixed binaries, unknown formats |
csv-input | CSV/TSV integrator uploads |
json-input | JSON integrator uploads |
Downstream nodes and node-output-query filters reference these names.
Ingest paths
| Source | Notes |
|---|---|
| HEAT Capture app | Protobuf DataPacket frames; multiple origin_uuid per session |
| v2 public API | HTTP upload to session |
| HEAT toolkit | External developer uploads |
| Control Centre | Operator manual upload |
See Ingests and Capture session templates.
Downstream platform nodes
| Route | Typical chain |
|---|---|
| Capture | capture-discovery (leaf), system-protobuf-extract, Arbex |
| Tabular | system-tabular-to-dataservice |
| JSON | system-arbex-js, heat-system-dataservice-envelope |
Related
Opens your browser's print dialog. Choose "Save as PDF" as the destination.