Copy node

The copy function allows you to duplicate nodes within a flow or across different flows, enabling reuse of existing configurations.

The copy function can also be used across different flows, allowing reuse of existing configurations.

Copy a node

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

2. Press the dedicated copy button.

3. On the IO grid, right click with the mouse and select paste.

It is possible to copy multiple nodes at one time by pressing and holding the Ctrl button on the keyboard and selecting the nodes that you want to copy, then right click on one of these and press copy. When pasted, it also keeps the connections between the copied nodes.

Copy across flows

To copy nodes from one flow to another:

1. Open the source flow containing the nodes you want to copy.

2. Right click on the node(s) and select copy.

3. Open the target flow where you want to paste the nodes.

4. Right click on the IO grid and select paste.

The nodes will be duplicated with all their configuration settings preserved.

What gets copied

When you copy a node, the following elements are duplicated:

• Node configuration: All settings and parameters

• Variable mappings: Input and output variable references

• Custom logic: Any scripts or custom code

• Visual settings: Size, position (relative when pasting multiple nodes)

What doesn't get copied

The following elements are not copied:

• Node ID: A new unique ID is generated for the copied node

• Connections: Connections to nodes outside the selection are not preserved

• Node name: If pasting in the same flow, consider renaming to avoid confusion

Use cases

Template nodes

Create commonly used node configurations once and copy them across multiple flows:

• Standard validation nodes

• Common API call configurations

• Frequently used forms

Flow sections

Copy entire sections of flows:

• Error handling patterns

• Authentication sequences

• Data processing chains

Environment migration

Copy nodes from development to production flows while maintaining configuration consistency.

Best practices

• Rename copied nodes to reflect their specific purpose in the new context

• Review connections after pasting to ensure proper flow logic

• Update variables if needed for the new flow context

• Test thoroughly after copying to verify functionality

• Document patterns that you frequently copy for team knowledge

Next steps

• Delete nodes

• Add comments to organize nodes

• Manage variables

• Design flows