Feature Request
Currently, n8n allows users to manually add tags and highlight important execution data using the Execution Data node. However, there is no native way to dynamically store metadata or tags during workflow execution.
Problem Statement
Workflows often contain conditional branches, meaning not all executions follow the same path or reach the end of the workflow. When receiving a webhook, for example, an execution may stop at different points based on variable conditions. However, there is currently no way to automatically label or categorize an execution based on which branch it followed.
Right now, users must store this data externally (e.g., in a database or Google Sheets) or use custom workarounds with the Set or Function nodes.
Proposed Solution
Introduce a native mechanism to allow workflows to dynamically assign metadata to an execution, making it accessible in the execution logs. Possible solutions could include:
- Extending the Execution Data node to support automated data insertion.
- Providing an API endpoint to update execution metadata.
- Adding an option in workflow settings to define execution tags dynamically.
Use Case
- A workflow receives a webhook and processes the data based on conditions.
- Some executions stop at different branches due to conditional logic.
- The workflow should automatically tag or classify each execution based on the path it followed.
- This would help users easily track execution flow without manually inspecting logs.
- Improves debugging and analytics by categorizing executions dynamically.
Related Features
- Execution Data node
- Conditional branching (IF node, Switch node)
This feature would improve workflow automation by enabling dynamic classification and tracking of execution paths.