Log
The Log node writes a message to the workflow execution log. Use it for debugging, auditing, and tracking what's happening at each step.
Type: LOG / LOG_V2
Color: Blue (#2563EB)
Credits: None
Test module: No
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Log type | Select | Yes | Severity level: INFO, DEBUG, WARN, ERROR |
| Content | FX formula | Yes | The message to log; supports variables |
Log levels
| Level | When to use | Example message |
|---|---|---|
| INFO | Normal operations; track successful steps | Order processed successfully |
| DEBUG | Development; inspect data at a point in the workflow | Received payload with 5 fields |
| WARN | Something unexpected but not fatal | API returned 429 — retrying in 5s |
| ERROR | Something went wrong | Failed to create record — constraint violation |
How to use
Add a Log node anywhere in your workflow. Set the log type and write a message using the FX formula editor. Reference data from previous nodes with the variable picker.
Debug data flow
Insert Log nodes between other nodes to trace what data is flowing through:
Trigger → Log → Process → Log → Send Email
Each Log captures the data at that point, useful for finding where values go wrong.
Audit trail
Log important business events for compliance:
Trigger → Process → Create Record → Log (record created)
Error tracking
Log errors before sending alerts:
HTTP Request → If-Else (check status) →
Failure: Log (error details) → Send Alert
Viewing logs
Log messages appear in the Execution History. Click any execution to see all log entries with their timestamps and severity levels.
Filter by log level to find errors quickly; ERROR and WARN entries stand out from INFO/DEBUG.
Add Log nodes liberally during development, then remove them before publishing to production. They are your cheapest and fastest debugging tool, much simpler than adding Send Email to Yourself at every step.
Log messages are stored in the execution history and visible to all workspace members. Don't log sensitive data (passwords, API keys, PII) in production workflows.