I have many workflows with multiple triggers, and I want to filter executions by trigger for easier debugging.
The closest solution is adding an Execution data node after each trigger, but that requires too many extra nodes. I think this feature is essential for scaling workflows.
Quick follow-up here.
I always have multiple triggers for all my n8n automations, and I know a lot of n8n users do the same. Most times, it’s challenging to find certain executions based on specific triggers.
The only solution I see is using the Execution Data nodes, which I think is unnecessary, and this could be implemented nicely by default.
