External Output

Node ID: externalOutput · Role: Sink · Realtime config: no

Description

Re-publishes a filtered slice of pipeline data on a public TCP endpoint. Used by the editor’s External Output node so each external consumer sees only what is visually wired into it.

Inputs / Outputs

Inputs: (none)
Outputs: (none)

Config aliases

ExternalOutput, externalOutput, _external_output

Properties

No user-facing properties.

Example node definition

A full node definition in config.json looks like the block below. Paste it under the sinks key of your config, keyed by the node’s instance name (any identifier; it doesn’t have to match the node ID).

{
  "sinks": {
    "externalOutput": {
      "inputEndpoints": [],
      "settings": {}
    }
  }
}

Field reference

Field	Purpose
`inputEndpoints`	List of upstream endpoints this node connects to (`outEndpoint` / `dataEndpoint` values from upstream nodes).
`inputDataFilter`	Optional whitelist of data types. Messages whose type isn’t in the list are dropped at the subscriber.
`settings`	All user-configurable fields — see the Properties table above.

Connections can also be declared at the top-level connections array when settings.explicitConnections is true, as an alternative to filling inputEndpoints on each node.

Loading documentation…