For polymorphic ports, the list of accepted types. If non-empty, this port can accept any of these types and will adapt its behavior based on the connected type.
OptionaldefaultValue?: stringDefault value for this port when not connected (JSON-encoded). Only applicable for input ports.
Optional description explaining what this port is for.
Human-readable name displayed in the UI. Examples: "Target Position", "Bot", "Message".
OptionalelementType?: PortTypeFor list ports, the type of elements in the list. Only applicable when port_type is PORT_TYPE_LIST.
The identifier for this port. Used in edge connections (source_handle/target_handle). Examples: "value", "target", "bot", "exec_in", "exec_out".
For dynamic output ports, the ID of the input port to inherit type from. Used for polymorphic nodes where output type depends on input type.
Whether this input accepts multiple connections (Blender-style multi-input). When true, all connected values are collected into a list. Visually rendered as a pill/ellipsis shaped socket.
The data type this port accepts or produces.
Whether this input is required for the node to execute. Only applicable for input ports.
OptionaltypeDescriptor?: TypeDescriptorOptional generic type descriptor for parameterized types.
When present, provides richer type information than the flat port_type field.
For example, List
Definition of a port (input or output) on a node type. Describes the port's type, constraints, and display properties.