No Op (core.noop)

Passes items through untouched — json, binary attachments, and order all survive exactly as they arrived. That's the whole node.

Parameters

None.

What it's for

• A named waypoint on the canvas: give it a descriptive name and use it as a visual anchor or a stable place to inspect data mid-pipeline.
• A fan-in/fan-out junction: collect several branches into one edge (or split one into several) without touching the data.
• A placeholder while sketching — imported n8n structural nodes that have no Parallix equivalent also land as disabled No Ops.

Quirks & tips

• Like every node, it's skipped (not run with zero items) when its incoming branch produced nothing.
• Each output item's paired_item points at its input index — lineage is set, not merely copied.

Related

• Set — a passthrough that also reshapes.
• Merge — when the fan-in needs join semantics instead of a plain wire.