Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
22.5k Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

Output

Use this node to return a message from a sub-chain back to the parent rule chain that invoked it via a Rule Chain node. The name you give to the Output node becomes the connection label in the parent chain, so you can define multiple named outputs (e.g., Success, Failure, Valid) to drive different downstream flows.

This node requires no configuration. The node’s name (set when you add it to the rule chain) acts as the connection label used by the parent rule chain.

  1. The node receives a message within the current (sub-)rule chain.
  2. The message is returned to the parent rule chain that invoked this chain via a Rule Chain node.
  3. In the parent rule chain the message exits from the Rule Chain node via the connection whose label exactly matches this Output node’s name.

For example:

  • An Output node named Success routes messages via the Success connection in the parent chain.
  • An Output node named Failure routes messages via the Failure connection in the parent chain.
  • An Output node named Valid routes messages via the Valid connection in the parent chain.

This node has no output connections within its own rule chain. It returns messages to the parent rule chain where routing continues based on the Output node’s name as the connection label.

{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "EmptyNodeConfiguration",
"type": "object",
"properties": {},
"additionalProperties": false
}