A Node ID is a stable, human-readable identifier assigned to each node on the automation canvas. Unlike display names, a Node ID persists through renames and is the key used when one node references another programmatically.

Overview

A Node ID is a stable, human-readable identifier assigned to each node on the automation canvas. Unlike display names (which can be edited at any time), a Node ID persists across renames and is the key used when one node references another programmatically.

Every node on the canvas carries a Node ID — a short slug that uniquely identifies it within the automation. Node IDs make it possible to reference a specific node's output in conditions, formulas, and sub-automation calls without the reference breaking when someone renames the node's display label.

Common Use Cases

• Execution Tracking — Use the Node ID in logs and monitoring queries to pin a metric or error to the exact step that produced it, even after the automation has been updated.

• Connecting Nodes Internally — Reference a prior node's output by its Node ID in a formula or condition ({{node_id.output.field}}), so the reference stays valid if the display name changes.

• Versioning and Workflow Diffing — When comparing two versions of an automation, matching by Node ID rather than display name gives a stable view of which steps changed, which moved, and which were added or removed.

• Conditional Logic and Branching — In a Branch or Condition node, use Node IDs as targets so the routing logic is independent of how nodes are labeled in the UI.

Advantages of Using Node IDs

• Stability — The ID does not change when you rename a node, so downstream references never break.

• Precision — Disambiguates nodes that share a display name (e.g., two "Send Email" actions in the same automation).

• Scalability — Works correctly in large automations with dozens of nodes where display names alone are not enough context.

• Maintainability — A teammate reading the automation can trace a formula or condition back to the exact node without decoding display-name conventions.

Notes

Node IDs are the reliable way to wire automations together when you need references that survive edits. To make the most of them:

• Set a meaningful Node ID when you add a node — the default is auto-generated and not descriptive.

• Use Node IDs (not display names) in formulas and conditions from the start; changing a display name later will not break anything if the ID was used.

• Keep Node IDs lowercase with hyphens (e.g., fetch-zendesk-ticket, send-slack-alert) to match the convention used across the platform.

• Audit Node IDs before publishing a version — a clear ID makes version diffs readable without opening each node.

A consistent Node ID scheme is the difference between an automation that is easy to debug six months later and one that requires reopening every node to understand the flow.