Custom Nodes
When no catalog node does what a step needs, write your own. A custom node is a Python function with an editor, inputs and outputs you define; once saved it appears in the builder's node list beside the catalog nodes.
Open Workflows > Node Manager. The counts at the top are the nodes you can see: the platform catalog (System nodes) and the custom nodes you own or that are shared with you.
Creating a Node
Click Create Node and fill in the tabs:
| Tab | What it holds |
|---|---|
| Basic Info | Category and Label (as the node shows in the builder), Type (the identifier workflows use: letters, numbers, hyphens and underscores, fixed once the node is created), Description, an MCP Description STAN reads to decide when to use the node, tags, the node's Version (semantic, starting at 0.0.1) and its icon |
| Python Code | The node's code: upload a .py file, or click Or write the code here and write it in the editor. Requirements (pip packages, one per line) go below it |
| Documentation | A README for people using the node, in Markdown |
| Input / Output | The fields the node takes and returns, which the builder offers when you map one node's output to another's input |
| Permissions | Who else may use or edit the node |
| Resources | The CPU, memory and GPU the node runs with |
Click Save. The code is required.
Changing a Node
Edit any tab and click Save. When the change touches the node's code, requirements or documentation, the node's Version must be raised first (+ bump): published code never changes under the same version. A change to anything else (description, label, input and output fields, resources) saves under the same version.
Version History
Every save records a version of the node, numbered from 1 (the node as it was created). Click the Version button at the top of the node to open its history: each version with its name, type (minor or major), tag, when it was made and by whom; the node's current version is marked Current.
- Create Version records the node's present state as a named version, with an optional description, type and tag (for example
stable). Search finds versions by name, description or tag. - Select a version to see the node as it was then (category, type, label, author, node version, inputs and outputs).
- Restore makes that version's state the node's next version, named Restored from vN. Nothing is lost: the state it replaces is the version it was saved as, and you can restore that in turn. If the node changed since you opened its history (someone else saved it), the restore is refused; reopen the history and try again.
Deleting a Node
Delete removes the node, its published files and its version history. A node a workflow or agent still uses cannot be deleted; remove it from those first.