Skip to main content

Log

Controlled node

Overview

The Log node writes a message to the workflow log. It is a simple but essential debugging tool that lets you trace execution flow and inspect values as they move through a workflow.

Each log entry is written with a severity level and is automatically tagged with the node's id and type, so you can tell exactly which node produced the message. After the message is written, the node fires its Done event, allowing it to sit in the middle of an event chain without interrupting execution.

Log levels

LevelDescription
DebugLow-level diagnostic information, useful while developing a workflow.
InfoGeneral informational messages about workflow progress.
WarnIndicates something unexpected that did not stop the workflow.
ErrorIndicates a failure or serious problem.

Runtime behavior

  • The node only runs when its Run event is triggered; all other incoming events are ignored.
  • The Message value is converted to a string before being written, so non-text values (numbers, booleans, objects) can be connected directly and will be stringified.
  • If Level is not connected and not set on the node, it defaults to debug.
  • If Message is not connected and not set on the node, an empty string is logged.
  • The Done event fires immediately after the message is written to the log.

Inputs

InputTypeDescriptionDefault
LevelEnumThe severity level of the log entry. One of debug, info, warn, or error.debug
MessageTextThe message to write to the workflow log. Non-text values are converted to strings.-
RunEventTriggers the node to write the log entry.-

Outputs

OutputTypeDescription
DoneEventFires after the message has been written to the workflow log.

Example

A common use for the Log node is to trace a value as it moves through a workflow:

  1. Add an AI Write node that generates some text.
  2. Add a Log node and connect the AI Write node's Done event to the Log node's Run event.
  3. Connect the AI Write node's Output to the Log node's Message input.
  4. Set the Log node's Level to Info.
  5. Run the workflow — the generated text will appear in the workflow log, tagged with the Log node's id.

Because the Log node fires a Done event after writing, you can also connect Done to the next node in your workflow and use Log as a pass-through checkpoint in the middle of an event chain.