Status
Monitors and captures status updates from other nodes in your flows.
Where and why do we use the Status node?
The Status node lets you programmatically react to state changes in other nodes by capturing their status updates. While many nodes display status information visually below themselves in the editor, the Status node converts these updates into message flows you can process. This is essential for building automated error handling, creating custom monitoring dashboards, tracking node performance, or implementing logic that responds to operational conditions like queue sizes or connection states.
Modes of operation
The Status node can monitor status updates from different scopes:
All Nodes
Captures status updates from all nodes in the same tab or flow. This provides flow-wide visibility into node states, useful for centralized monitoring or logging.
Same Group
Limits status capture to nodes within the same group as the Status node. Use this when you want isolated status monitoring for specific sections of your flow that are grouped together.
Selected Nodes
Captures status from specific nodes you choose. This gives you fine-grained control over which nodes' status updates are monitored, useful when you only care about particular nodes or want different handling for different node types.
How the node handles messages
When a monitored node updates its status, the Status node emits a message object containing status information. The node creates a new message flow that you can use to react to status changes programmatically.
The message object emitted by the Status node contains:
- status.text - the status text displayed below the node
- status.fill - the color of the status indicator (red, green, yellow, blue, grey)
- status.shape - the shape of the status indicator (ring or dot)
- status.source - object containing information about the node that generated the status:
- id - the source node id
- type - the type of the source node
- name - the name, if set, of the source node
This information enables you to implement sophisticated monitoring logic, including conditional responses based on which node changed status, what the status indicates, or patterns of status changes over time.
Examples
Monitoring delay node queue size
The Status node tracks the number of messages queued in a delay node. This example captures status updates from the delay node and processes them to monitor queue depth, useful for detecting backpressure or triggering alerts when the queue grows too large.
Connection state monitoring
Monitor the connection status of MQTT or other connection-based nodes. This example shows how to capture connection state changes and use them to trigger reconnection logic, send alerts, or update application state based on connectivity.
Node Documentation
Report status messages from other nodes on the same tab.
Outputs
Details
This node does not produce a payload.
By default the node reports status for all nodes on the same workspace tab. It can be configured to selectively report status for individual nodes.