Comment

Overview

The Internal Comment Component (identified in the interface by the technical title Comment) is a utility node focused exclusively on documentation, visual organization, and flow governance. Unlike messaging nodes, this component does not interact and is not visible to the end customer. Its main function is to serve as visual support so developers and managers can enter technical notes, business rule descriptions, pending-task warnings, or journey mapping within the automation canvas itself.

Configuration Parameters

The block settings manage the text formatting and visual identity of the note in the editor:

• Comment: Rich text editor (rich text) where the administrator types the desired note, explanation, or documentation. It provides a native toolbar with options such as bold, italic, strikethrough, horizontal lines, headings, links, block quotes, insertion of code snippets (code blocks), tables, and ordered lists.

• Preview: Dynamic area that renders the formatted text in the editor in real time, showing exactly how the note will appear to the team on the design map.

• Color: Color tone selector bar (shown in purple in the image). It allows changing the highlight color of the container or the node header on the flow map.

Visual Builder

The graphical interface is optimized for readability and spatial organization within the automation map:

• Standalone Rich Text Editor: The builder offers full word processor-level formatting tools so complex data (such as API to-do lists) can be documented in a structured, clean manner.

• Node Without Line Connectors: In the graphical flow editor, this component acts as an isolated floating block. It has no physical input or output ports, because it is not part of the contact's transactional workflow. It is freely positioned next to action nodes to explain what that specific branch of the bot does.

Special Operators

The logical properties of this component manage purely static indexing and the visual control of projects:

• Color-Coding System: The field property Color allows agile teams to create quick visual moderation patterns on the canvas (e.g., use blocks Red to document known errors, Green to indicate approved business rules, or Yellow for pending tasks).

• Static Processing Without Infrastructure Impact: The automation engine completely ignores this component during a customer's real-time journey execution. The node consumes no transactional memory, generates no latency, and does not process dynamic scope variables.

Practical Examples

The table below shows classic scenarios of how to configure and spread the comment blocks to document a professional automation:

Selected Block Color	Formatted Content in the Comment	Purpose of the Note on the Canvas	Practical Use Case
Purple	### Lead Distribution Rule - Sector 1: Retail Sales\n\n\n\n- Sector 2: Wholesale Sales	Explain the criteria of a nearby Switch Case conditional block.	Make it clear to new administrators which mathematical parameters guide the bot's sector division.
Red	> ⚠️ **WARNING:** The API Token below expires every 90 days. Next renewal: 15/09/2026.	Emit critical infrastructure or maintenance warnings for the team.	Pin a red visual alert next to a Code or Webhook component to remind the support team about key updates.
Gray	*Flow built by developer Carlos in June/2026. Version 2.4.*	Identify authorship, change history, and script version.	Keep a static header at the top of the flow functioning as a project automation logbook.