Delete node

This page describes how to delete nodes from IO flows.

Delete a node

Warning: Deleted nodes cannot be restored, and any configuration or settings within them will be permanently lost.

1. On the IO designer, right click on the desired node.

2. Press the dedicated delete button.

3. Confirm the deletion by pressing the DELETE button.

It is possible to delete multiple nodes at one time by pressing and holding the Ctrl button on the keyboard and selecting the nodes that you want to delete, then right click on one of these and press delete.

Before deleting

Consider the following before deleting a node:

Check connections

• Review which nodes connect to the node you're deleting
• Identify any outputs that will become disconnected
• Plan how to reconnect the flow after deletion

Consider alternatives

Instead of deleting, you might:

• Disable connections temporarily to test flow changes

• Create a flow version before making destructive changes

• Move the node to a comment area labeled "Unused" for future reference

Save configuration

If you might need the node configuration later:

• Copy the node before deleting

• Export the flow to preserve a backup

• Document any custom configurations

After deletion

After deleting a node:

1. Reconnect the flow: Link any disconnected nodes

2. Test the flow: Verify that the flow still functions correctly

3. Review variables: Check if any variables were only set by the deleted node

4. Update documentation: Note what was removed and why

Deleting multiple nodes

When deleting multiple nodes:

• Select all nodes you want to delete using Ctrl+Click

• Right click on any selected node

• Choose delete and confirm

All selected nodes and their internal connections will be removed. Connections to nodes outside the selection will be disconnected.

Impact on flow

Deleting a node affects:

• Flow execution: The removed step will no longer execute

• Variables: Variables set by the deleted node will no longer be available

• Connections: All connections to/from the node are removed

• Flow logic: Conditional branches may need adjustment

Common scenarios

Simplifying flows

Remove unnecessary nodes that don't add value:

• Redundant validation nodes

• Obsolete processing steps

• Deprecated API calls

Removing test nodes

Clean up nodes used during development:

• Debug output nodes

• Test data generation nodes

• Temporary logging nodes

Refactoring

Remove nodes when restructuring flows:

• Consolidating multiple nodes into one

• Replacing with more efficient nodes

• Updating to newer node versions

Best practices

• Test first: Use flow versions to test deletion impact

• Document changes: Note what was deleted and why

• Review dependencies: Check for nodes depending on deleted node's outputs

• Clean up comments: Remove or update comments referring to deleted nodes

• Communicate changes: Inform team members of significant deletions

Next steps

• Copy nodes

• Add comments

• Flow versioning

• Design flows