Skip to main content

Node Parameters

This guide covers how to define node parameters, parameter types, and advanced configuration options.

INodeProperties Interface

Node parameters are defined using the INodeProperties interface.
Basic Parameter Structure

Parameter Types

String

Text input fields.

Number

Numeric input fields.
Number Parameter

Boolean

Checkbox or toggle fields.
Boolean Parameter

Options

Dropdown selection from static or dynamic list.
Static Options

MultiOptions

Multi-select dropdown.
MultiOptions Parameter

Collection

Key-value pair collection.
Collection Parameter

FixedCollection

Structured collection with named groups.
FixedCollection Parameter
Access in execute:
Accessing FixedCollection

ResourceLocator

Advanced parameter for selecting resources by ID, URL, or list.
ResourceLocator Parameter
Implement search method:
List Search Method

DateTime

Date and time picker.
DateTime Parameter

JSON

JSON editor.
JSON Parameter

Color

Color picker.
Color Parameter

Hidden

Hidden field (useful for credentials).
Hidden Parameter

Display Options

Control parameter visibility based on other parameters.

Advanced Type Options

Multiple Values

Allow multiple instances of a parameter.
Multiple Values

Load Options Dependencies

Make options depend on other parameters.
Dependent Options
Implement dependent load:
Dependent Load Method

Code Autocomplete

Provide autocomplete in code editors.
Code Autocomplete

Validation

Validate parameter values.

Built-in Validation

Type Validation

Regex Validation (ResourceLocator)

Regex Validation

Routing Configuration

For declarative nodes, define HTTP routing.
Routing Configuration

Special Parameter Types

Notice

Display informational text.
Notice Parameter

Button

Trigger custom actions.
Button Parameter
Handle button action:
Button Action Handler

Filter

Advanced filtering interface.
Filter Parameter

ResourceMapper

Map input fields to service fields.
ResourceMapper Parameter
Implement resource mapper method:
Resource Mapper Method

Best Practices

  • Use clear, descriptive displayName values
  • Use camelCase for parameter name
  • Add helpful description text
  • Use consistent naming across similar parameters

See Also