Category ID for organizing nodes in the palette. References CategoryDefinition.id from GetNodeTypesResponse. Examples: "triggers", "actions", "math", "logic", "flow".
Optional color hint for the node (hex color code). Used for visual distinction between node categories.
Whether this node is deprecated and should be avoided.
If deprecated, message explaining what to use instead.
Description of what this node does. Displayed in tooltips and node palettes.
Human-readable name displayed in the UI. Examples: "On Tick", "Pathfind To", "Add".
Optional icon identifier for rendering. Can be an icon name or emoji.
The input ports for this node type. Includes both data inputs and execution inputs.
Whether this node is expensive (slow, may block). Used for visual warnings in tick-path analysis.
Whether this is a layout node (reroute, frame, etc.). Layout nodes have special minimal rendering and don't execute logic.
Whether this is a trigger node (entry point for execution). Trigger nodes have no execution input and start script flows.
Keywords for searching/filtering nodes in the palette.
The output ports for this node type. Includes both data outputs and execution outputs.
Whether this node can be muted (bypassed during execution). When muted, inputs pass through to outputs unchanged.
Whether this node supports inline preview of its output.
The unique type identifier for this node. Examples: "trigger.on_tick", "action.pathfind", "math.add".
Complete definition of a node type. Contains all metadata needed to render the node in an editor and validate its connections without hardcoded client knowledge.