Share on print

Understanding the Add Tag and Clear Tag Nodes: Managing Asset Tags

What are the Add Tag and Clear Tag Nodes?

The Add Tag node applies a tag to an asset, while the Clear Tag node removes one. They're covered together here since they perform the same action in opposite directions.

Add Tag and Clear Tag Nodes


When Should I Use Them?

Add Tag and Clear Tag are useful whenever a Workflow should update an asset's tags automatically, rather than relying on someone doing it manually. A real example: a Workflow that listens for an asset being marked as recovered, then uses Clear Tag to remove its "stolen" tag before notifying the customer. Common uses include:

  • Automatically tagging an asset when a specific event occurs, such as tagging a vehicle as "in maintenance."
  • Removing a tag once the situation it represented has resolved, such as clearing a "stolen" tag once an asset is recovered.
  • Keeping tag-based filtering elsewhere in your platform accurate and up to date automatically.

Why Does It Matter?

Tags are often used elsewhere in your platform for filtering, reporting, and other Workflows. Keeping them accurate and current without manual upkeep means the rest of your setup that depends on those tags stays reliable.


How Do I Use Them?

  1. Drag the Add Tag or Clear Tag node from the right-hand column onto the canvas, and place it at the point in your Workflow where the tag should be added or removed.
  2. Hover over the node and select edit to configure it.
  3. Select the tag to add or remove.
  4. Connect the green ball onward if your Workflow continues after the tag is updated.

Add Tag and Clear Tag Nodes settings


Common Pitfalls

  • Adding without a corresponding clear: if a tag is meant to reflect a temporary state, make sure there's a Clear Tag step elsewhere in the Workflow to remove it once that state ends.
  • Tag name mismatches: make sure the tag selected here matches exactly what other Workflows or filters expect.
  • Listener node not configured correctly: these nodes can only act on what actually makes it through the Listener node in the first place.

Related Articles

Still Need Help?

Contact our Support team. We are always happy to help.