Read the canvas: nodes, ports and the traffic-light states
Walk a real workflow and watch the lights change
Every node in KNIME carries a small traffic light at its base: red means not yet configured, yellow means configured and ready, green means executed successfully. The triangles on a node's sides are its ports — data goes in the left, out the right. Learning to read these at a glance is what turns the canvas from a wall of boxes into something you can debug.
- 1 Open the two-node workflow you built, or drag a fresh CSV Reader and Row Filter onto the canvas.
- 2 Look at each node's traffic light before you configure it — a freshly dropped node shows red.
- 3 Configure the CSV Reader and watch its light turn yellow (configured, ready to run).
- 4 Run just that node and watch it turn green (executed). Notice the output port now carries a data table.
- 5 Hover over the input and output ports (the triangles) to see what kind of data each one expects or produces.
You can name, for any node, whether it is red, yellow or green, and point to its input and output ports.
The canvas anatomy: readers, transformers and the wires between them
A larger KNIME workflow is the same grammar repeated. Sources on the left (CSV, Excel, Snowflake, database readers) feed transformers in the middle (Concatenate, Column Renamer, filters) which feed analysis and output nodes on the right. As you add more nodes, you will see how the ports and traffic-light states let you read the whole pipeline at a glance.
Reading a KNIME canvas comes down to three things: nodes (each one step), ports (the triangles where data enters and leaves), and the traffic light (red = not configured, yellow = ready, green = executed). Because every step and every connection is visible on the canvas, the workflow is self-documenting — which is exactly why it is reproducible and shareable as a recipe rather than buried in code.
- ?Given a node showing a yellow light, what has happened and what has not?
- ?How can you tell, just by looking, where a workflow would stop if one node failed?
- ?Why does having every step visible as a node make a workflow easier to share than a script with the same logic?
Add a third node and keep the lights green
Reading the states is only useful if you can act on them. Extend your workflow by one node and use the traffic lights to confirm each step before moving on.
Add one more transformer node after your Row Filter, wire it in, and drive the whole chain to all-green.
- 1 Drag a third node onto the canvas (for example a Column Renamer) and connect it to the Row Filter's output port.
- 2 Configure it and confirm its light goes from red to yellow.
- 3 Execute the workflow and confirm every node is green.
- 4 Open the final node's output table to check the result is what you expected.
A three-node workflow where every node is green and the final output table is correct.