Note Node

TL;DR:

• What: Leave notes or documentation for yourself or teammates directly on the canvas.
• When: You need to explain complex logic or mark to-do items.
• Result: Nothing. Notes are editor-only and do not affect the bot.

What it does

The Note node lets you add internal comments directly to the scenario canvas. It is useful when a flow becomes large and you want to explain the purpose of a section, leave a reminder, or make the scenario easier for teammates to understand. Notes are visible only inside the editor and do not affect what users see in Telegram.

When to use it

• ✅ Explaining complex logic — Describe what a group of nodes does.
• ✅ Leaving reminders — Mark unfinished parts or TODOs.
• ✅ Organizing large scenarios — Visually separate sections with labels.

When NOT to use it

• ❌ Routing the conversation — Use a Message or Condition node instead.
• ❌ Storing data — Use an Actions node instead.

What you can configure

In a Note node, you can write free-form text that appears directly on the scenario canvas.

You can use it for:

• Explaining what a group of nodes does.
• Leaving reminders or TODOs.
• Documenting why a branch exists.
• Separating large scenario sections visually.

Output and behavior

The Note node is editor-only.

• Next step behavior: None. It has no input or output ports and cannot be connected to the flow.
• User-facing result: None. Bot users never see Note nodes.
• Side effects: None. It does not send messages, update variables, add tags, or trigger actions.

Examples

Example 1: Mark unfinished work

Goal: Mark a part of the scenario as unfinished.
Setup: Add a Note node with "TODO: connect fallback path before publishing."
Result: The reminder stays visible on the canvas for you and your team.

Example 2: Explain a complex section

Goal: Explain a complex onboarding section.
Setup: Add a Note node near the related nodes and describe what this section does, such as "This branch handles users who selected paid access but have not completed payment yet."
Result: Other editors can understand the scenario faster without opening every node.

Common pitfalls

• Expecting a Note to affect the bot → Notes are editor-only. Fix: Use Message, Condition, Actions, or another functional node for real bot behavior.

• Using notes instead of clear node names → Notes help, but they should not replace clear labels. Fix: Name important nodes clearly and use notes for extra context.

• Writing sensitive data in notes → Notes may be visible to workspace members with editor access. Fix: Do not store API keys, passwords, or private customer data in notes.

FAQ

• Q: Can Telegram users see Note nodes?
  A: No. Notes are visible only inside the scenario editor.

• Q: Can a Note node connect to other nodes?
  A: No. Note nodes have no input or output ports.

• Q: Does a Note node affect publishing?
  A: No. It is ignored by the runtime and does not change bot behavior.

• Q: Can I use notes for TODOs?
  A: Yes. Notes are a good place for internal reminders while building or reviewing a scenario.

Related nodes

• Message Node — Use when you want to send visible text to Telegram users.
• Condition Node — Use when you need real branching logic.
• Actions Node — Use when you need to update variables, tags, or trigger background actions.