Documentation
WorkflowsNEW

Workflow Saved Nodes

Save a configured canvas node to your library, export saved nodes as ZIP for backup or sharing, and import node packages.

This guide explains how to save a configured canvas node to your library, export saved nodes for backup or sharing, and import a node package so saved nodes appear in the workflow editor.


Overview

A saved node is a reusable template stored in your library. It appears in the workflow graph editor’s left sidebar under Saved workflow nodes, grouped by category. You can drag it onto the canvas like a built-in component.


Save a Node to the Library

Steps

  1. Open the workflow graph editor for the workflow you are editing.
  2. Select the node on the canvas you want to turn into a reusable template.
  3. Open the node details drawer on the right (it shows the node name and Configure the node parameters).

Workflow canvas node python_code with floating toolbar above it; the Edit control is highlighted with tooltip Edit to open the node details drawer

  1. Click Save to Library.

Node details panel for python_code: Configure the node parameters with Save To Library highlighted in the header

Form Fields

In the Save to Library dialog, fill in:

FieldRequiredNotes
NameYesA clear, unique name for the library entry.
CategoryYesUsed to group entries in the sidebar (for example Library, Parsers, Enrichers).
TagsNoOptional labels; type a tag and press Enter to add more.
AuthorYesWho owns or maintains this template.
VersionYesFor example 1.0.0.
IconYesAn image file for the node in the sidebar.
Is uniqueYesWhen on, only one instance of this node type is allowed per workflow when placed from the library.
DescriptionNoOptional longer description.

Click Save to Library in the dialog footer to submit, or Cancel to close without saving.

Tips

  • Configure the node on the canvas before saving to the library; the library entry captures that configuration as a starting point for new placements.
  • Editing the library template later does not automatically change nodes that were already placed on workflows.

Export Saved Nodes

Export downloads a ZIP file containing the selected saved workflow nodes from the library. Use it for backup, sharing with your team, or importing on another environment.

Steps

Stay in the workflow graph editor. In the left sidebar, scroll the node list until you see the heading Saved workflow nodes.

Export One Node

  1. Click the saved node card so its toolbar appears.
  2. Click Download node.

Saved workflow nodes: Process Input card with toolbar showing Select node, green Download node icon highlighted, delete, and link actions

Export Several Nodes at Once

  1. On each card you want, click Select node.

Saved workflow nodes sidebar: Process Input card with toolbar showing Select node checkmark, Download node, delete, and link actions

  1. When at least one node is selected, a download icon appears in the row with the Search nodes field. Click it to download a single ZIP containing all selected nodes.

Saved workflow nodes search row: Search nodes field with magnifying glass, green download icon, and clear selection X

Note

To clear the selection, use the clear selection control (X) next to the download icon.

Result

Your browser saves a ZIP file.


Import Saved Nodes

Import installs saved node packages from a ZIP file into the system so they show up under Saved workflow nodes when you edit a workflow.

Steps

Import is done from Settings, not from the graph editor:

  1. Open Settings.
  2. Open the Store tab.
  3. Select the Workflow Saved Nodes sub-tab.
  4. Click Import and choose a .zip file (compressed package of saved nodes, the same kind produced by Export).

Settings Store: Workflow Saved Nodes tab selected with Import in the toolbar; main area shows No Objects Found

After a successful import, open any workflow’s graph editor and confirm the nodes appear under Saved workflow nodes.

If Something Fails

  • Duplicate id: If a node in the package already exists with the same identifier, that item may be skipped or reported as a conflict. Resolve duplicates by removing the old entry or using a different package, per your team process.
  • Missing node types: The environment must support the same underlying node types (components) as the system where the package was built. If a type does not exist here, import may fail for that entry; check any result or error message shown after import.