Logging in Unify Automations lets you emit structured messages at configurable severity levels from any node during a run. Use it to capture key decision points, variable values, and error context — all visible in each node's Logs tab after execution.
Overview
Logging in Unify Automations lets you emit structured messages from any node during a run — capturing custom diagnostics, variable values, and decision points that are then visible in the node's Logs tab.
Every node can be configured to emit one or more log messages at any logging level. These messages are visible in the run's node detail view under the Logs tab, and can be filtered by level to focus on errors or trace the full execution path. Logging is configured per node; you control what gets logged, when, and whether sensitive fields are masked.
How Logging Levels Work
Logging levels form a hierarchy. The level configured in Automation Settings defines the floor — a node can only log at that level or above it:
Level | Use for |
|---|---|
Error | Fatal conditions that mean the node's output cannot be trusted |
Warn | Unexpected conditions that were recovered from but should be reviewed |
Info | Normal milestone events (process started, record found, decision made) |
Debug | Detailed diagnostic data for development and debugging |
Trace | The most granular level — full input/output snapshots and internal state |
Note: A node cannot log at a level below the level configured in Automation Settings. If the automation-wide level is set to Info, nodes cannot emit Debug or Trace messages even if configured to do so.
Steps to Configure a Log Message
Select the node you want to add logging to on the canvas.
Open the node's configuration panel and navigate to the Logging section.
Choose the Log Type (Error, Warn, Info, Debug, or Trace).
Configure the Message — combine static text with data pills from earlier steps to include runtime values.
Set Only Log When conditions if the message should be emitted only in specific situations (e.g., only when a field is empty).
Select any Fields to Mask to prevent sensitive values (API keys, PII) from appearing in the log output.
Enable Only Log on Failure if the message should be emitted only when the node errors, not on successful runs.
Notes
Logging is the fastest way to add observability to an automation without adding Code nodes. To make the most of it:
Log the key decision inputs at Info level (which branch was taken, what value triggered a condition) so runs are interpretable without replaying them.
Use Warn for conditions that are handled but unexpected — they indicate potential data quality issues worth tracking over time.
Mask fields that contain credentials or PII before the run reaches production — masked values appear as *** in the log output.
Use "Only Log on Failure" for verbose Trace messages — it keeps successful-run logs clean while preserving the full trace for debugging failures.
Well-placed log messages make the difference between an automation that is easy to diagnose and one that requires a full replay to understand what happened.