Skip to main content
Version: 2.2-dev

Ignition Nodes

Ignition by Inductive Automation is a widely adopted industrial automation platform. MaestroHub connects to Ignition Gateways and exposes read, write, and browse capabilities as pipeline nodes — enabling tag-level data access within your automation workflows.

Configuration Quick Reference

FieldWhat you chooseDetails
ParametersConnection, Function, Function Parameters, Timeout OverrideSelect the Ignition connection profile, function, configure function parameters with expression support, and optionally override timeout.
SettingsDescription, Timeout (seconds), Retry on Timeout, Retry on Fail, On ErrorNode description, maximum execution time, retry behavior on timeout or failure, and error handling strategy. All execution settings default to pipeline-level values.

Ignition Read node configuration

Ignition Read Node

Ignition Read Node

Read tag values from an Ignition Gateway. Supports reading multiple tags in a single execution with full quality and timestamp metadata.

Supported Function Types:

Function NamePurposeCommon Use Cases
Ignition Read (ignition.read)Fetch current tag values from Ignition GatewayEquipment telemetry, process monitoring, quality checks, batch data collection

Node Configuration

ParameterTypeRequiredDescription
ConnectionSelectionYesIgnition connection profile to use
FunctionSelectionYesRead function from the selected connection
Function ParametersDynamicVariesAuto-populated from the function schema. See your Ignition connection functions for full parameter details.
Timeout OverrideNumber (seconds)NoOverride the default function timeout

Function parameters for Read:

ParameterTypeRequiredDescription
tagsArray of stringsYesTag paths to read (at least 1). Uses Ignition tag path format: [provider]Path/To/Tag

All function parameters support expression syntax ({{ expression }}) for dynamic values from the pipeline context.

Output Structure

{
"success": true,
"functionId": "<function-id>",
"data": {
"values": [
{
"path": "[default]Line1/Temperature",
"value": 78.5,
"quality": "Good",
"timestamp": 1704067200123
},
{
"path": "[default]Line1/Pressure",
"value": 145.2,
"quality": "Good",
"timestamp": 1704067200150
}
]
},
"durationMs": 42,
"timestamp": "2026-01-15T08:30:00Z"
}
FieldTypeDescription
successbooleantrue when the function executed without errors
functionIdstringID of the executed function
data.valuesarrayArray of tag read results
data.values[].pathstringFull tag path including provider (e.g., "[default]Line1/Temperature")
data.values[].valueanyCurrent tag value — type depends on the Ignition tag data type (Boolean, Int, Float, String, etc.)
data.values[].qualitystringQuality indicator ("Good", "Bad", "Uncertain")
data.values[].timestampnumberUnix timestamp in milliseconds when the value was read
data.values[].errorstring(Only present on error) Error message if the tag read failed
durationMsnumberExecution time in milliseconds
timestampstringISO 8601 / RFC 3339 UTC timestamp

Ignition Write Node

Write values to Ignition Gateway tags. Supports writing multiple tags in a single execution and dynamic values through expression syntax.

Supported Function Types:

Function NamePurposeCommon Use Cases
Ignition Write (ignition.write)Send values to Ignition tagsUpdate setpoints, write control commands, push recipe parameters

Node Configuration

ParameterTypeRequiredDescription
ConnectionSelectionYesIgnition connection profile to use
FunctionSelectionYesWrite function from the selected connection
Function ParametersDynamicVariesAuto-populated from the function schema. See your Ignition connection functions for full parameter details.
Timeout OverrideNumber (seconds)NoOverride the default function timeout

Function parameters for Write:

ParameterTypeRequiredDescription
dataArray of objectsYesArray of path/value pairs to write (at least 1)
data[].pathStringYesTag path to write to — must specify a full tag path, not just the provider (e.g., [default]Motor1/Speed, not [default])
data[].valueAnyYesValue to write

All function parameters support expression syntax ({{ expression }}) for dynamic values from the pipeline context.

Output Structure

{
"success": true,
"functionId": "<function-id>",
"data": {
"results": [
{
"path": "[default]Motor1/Setpoint",
"success": true,
"quality": "Good"
},
{
"path": "[default]Motor1/Command",
"success": false,
"quality": "Bad"
}
],
"successCount": 1,
"failureCount": 1
},
"durationMs": 15,
"timestamp": "2026-01-15T08:30:00Z"
}
FieldTypeDescription
successbooleantrue when the function executed without errors
functionIdstringID of the executed function
data.resultsarrayPer-tag write results
data.results[].pathstringIgnition tag path
data.results[].successbooleanWhether this tag was written successfully
data.results[].qualitystringQuality indicator for the write result
data.successCountnumberNumber of tags written successfully
data.failureCountnumberNumber of tags that failed
durationMsnumberExecution time in milliseconds
timestampstringISO 8601 / RFC 3339 UTC timestamp
Safety First

Always implement validation and safety checks before writing to industrial equipment. Consider adding condition nodes to verify values are within safe ranges.


Ignition Browse Node

Browse the Ignition Gateway tag hierarchy to discover available tags. Useful for dynamic tag discovery, building tag catalogs, and verifying tag structure within pipelines.

Supported Function Types:

Function NamePurposeCommon Use Cases
Ignition Browse (ignition.browse)Traverse Gateway tag hierarchyTag discovery, catalog building, structure verification

Node Configuration

ParameterTypeRequiredDescription
ConnectionSelectionYesIgnition connection profile to use
FunctionSelectionYesBrowse function from the selected connection
Function ParametersDynamicVariesAuto-populated from the function schema. See your Ignition connection functions for full parameter details.
Timeout OverrideNumber (seconds)NoOverride the default function timeout

Function parameters for Browse:

ParameterTypeRequiredDefaultDescription
pathStringNo""Tag path to browse. Empty string browses from the root. Uses format [provider]Path/To/Folder.
limitNumberNo1000Maximum number of nodes to return (1–10,000)

All function parameters support expression syntax ({{ expression }}) for dynamic values from the pipeline context.

Output Structure

{
"success": true,
"functionId": "<function-id>",
"data": {
"path": "[default]Plant1/Line1",
"nodes": [
{
"name": "Temperature",
"path": "[default]Plant1/Line1/Temperature",
"type": "AtomicTag",
"dataType": "Float8",
"hasChildren": false
},
{
"name": "Motors",
"path": "[default]Plant1/Line1/Motors",
"type": "Folder",
"hasChildren": true
}
],
"truncated": false
},
"durationMs": 85,
"timestamp": "2026-01-15T08:30:00Z"
}
FieldTypeDescription
successbooleantrue when the function executed without errors
functionIdstringID of the executed function
data.pathstringThe path that was browsed
data.nodesarrayArray of discovered nodes
data.nodes[].namestringDisplay name of the node
data.nodes[].pathstringFull tag path including provider
data.nodes[].typestringNode type: "Folder", "AtomicTag", "UdtInstance", or "UdtType"
data.nodes[].dataTypestringData type for tags (e.g., "Boolean", "Int4", "Float8", "String") — present on tag nodes
data.nodes[].hasChildrenbooleanWhether this node has child items
data.truncatedbooleantrue if results were limited by the limit parameter
durationMsnumberExecution time in milliseconds
timestampstringISO 8601 / RFC 3339 UTC timestamp

Tag Path Format

Ignition tag paths follow the format [provider]Path/To/Tag:

Example PathDescription
[default]Line1/TemperatureTemperature tag on Line 1 using the default provider
[default]Equipment/Motor1/SpeedMotor speed tag in an Equipment folder
[historian]Archive/DailyAvgTag from the historian provider

If no provider is specified, the [default] provider is used automatically.


Settings Tab

All Ignition node types share the same Settings tab:

SettingTypeDefaultDescription
DescriptionTextOptional description displayed on the node
Timeout (seconds)NumberPipeline defaultMaximum time the node may run before timing out
Retry on TimeoutTogglePipeline defaultAutomatically retry the node if it times out
Retry on FailTogglePipeline defaultAutomatically retry the node if it fails
On ErrorSelectionPipeline defaultError strategy: stop the pipeline, continue to the next node, or follow the error output path

When left at their defaults, these settings inherit from the pipeline-level execution configuration.