Logging
Recording events from a process or application to document what happened, at which stage, and with what result, at a defined level of detail.
On this page
Source content checked . English translation published 2026-10-27.
In business automation
A useful log includes a run ID, an action, and an understandable result. It should enable investigation without unnecessarily storing sensitive content or an entire customer document.
Examples
These examples illustrate a possible workflow. Adapt the connections and rules to your own systems.
Business process example
A process records that an attempt to update an order failed with a particular service code. The request ID and action duration are stored, but the API key and payment details are not written to the log.
Relevant tools
- n8n
- Execution history and operational data help with investigation, subject to your data retention settings.
What to check
- Logs without identifiers or with only a generic message are difficult to investigate. Set retention periods and viewing permissions too.