1. The Problem: Lack of Granularity in Saving
Current global execution saving settings in n8n (e.g., save all, save only on failure) are insufficient for workflows with multiple paths. Often, we want to save only executions that followed specific logic (e.g., a high-value order), without saving all successful ones (generating excessive data).
2. Proposed Solution: “Save Execution” Node
Create a node called “Save Execution”.
What it does: When reached in the flow, this node forces the current execution to be saved, even if the global workflow settings are configured not to save it (e.g., “save only on failure” and the execution was successful).
How it works: Simply add the node to the workflow path whose result you want to ensure is saved.
3. Essential Use Cases
Save only executions that processed financial transactions above a certain value.
Record executions where a critical business condition was met, even without a technical error.
Keep track of executions that followed a new logic branch during a testing phase.
4. Direct Benefits
Full Control: Decide exactly which executions to save.
Less Noise: Save only what is relevant, facilitating analysis.
Cost-Effective: Reduce data volume and storage costs.
Effective Auditing: Maintain important traces without unnecessary data.
5. Interaction with Global Settings
The “Save Execution” node complements global settings, allowing targeted exceptions to ensure saving when necessary, overriding the global rule if it is more restrictive.