Log node
The Log node records a structured event with a severity level, a rendered message, and a bag of context fields. Rows flow through the node unchanged, so a Log node is a side-channel: it observes the flow rather than changing what the flow produces. The Log node writes to the internal run log.
External destinations: HTTP webhook, Datadog, Grafana Loki, AWS CloudWatch, Splunk HEC, Elasticsearch / Kibana, Papertrail, Logtail.
When to use
- Emit a structured record from inside a flow so operators can see exactly what the run did without reading raw stdout.
- Attach row-derived context (customer id, order total, region) to every emitted event, redacted for sensitive keys.
- Gate emissions by a per-run minimum level so a
debug-heavy flow costs nothing in production.
Configure
- Level -
debug/info/warn/error/fatal. The level is a first-class field on the event, not a body prefix. - Message - a template string. Tokens
{{row.field}},{{exec.varName}},{{sys.runId}}use the same engine as the Notification node's message template. Warnings from failed interpolations land in the run log without breaking the run. - Fields - a grid of name / value rows. A value that is a bare
{{row.field}}preserves the underlying JS type (numbers stay numbers, booleans stay booleans). Anything else runs through the template engine and lands as a string. - Advanced -> Emission trigger -
Every row(default),When expression is truthy(render a small template; the result is truthy iff it is non-empty and not"false"/"0"/"no"), orOnly at or above run's minimum level. - Advanced -> Extra redaction keys - a comma-separated list layered on top of the platform's baseline redaction (
password,token,secret,api key,bearer,authorization). Case-insensitive exact key match.
Run launch: minimum log level
The run-launch modal exposes a Min log level dropdown (default info). Events whose configured level is below the run minimum are dropped at emission time, so a debug-heavy flow costs nothing when the run is launched at info. The setting is persisted per-project in the browser.
Run viewer
The run detail view surfaces a Log Events card next to the existing raw log. Every emitted event renders on one line with a colored level chip, the emitting node's name, and the message. A collapsible <details> block reveals the (redacted) fields object as pretty JSON. A level-filter row and a search box compose to narrow down large event lists.