# Executions - Filter by trigger or trigger node name

**URL:** <https://community.n8n.io/t/executions-filter-by-trigger-or-trigger-node-name/138756>\
**Category:** Feature Requests\
**Created:** [June 26, 2025, 12:27am UTC](https://community.n8n.io/t/executions-filter-by-trigger-or-trigger-node-name/138756 "2025-06-26T00:27:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brahimh](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/brahimh/32/37611_2.png) [@brahimh](https://community.n8n.io/u/brahimh)\
**Post date:** [June 26, 2025, 12:27am UTC](https://community.n8n.io/t/executions-filter-by-trigger-or-trigger-node-name/138756/1 "2025-06-26T00:27:10Z")

</div>

I have many workflows with multiple triggers, and I want to filter executions by trigger for easier debugging.

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/8/d/8dfe88b37cf23ffe1ccb12eb4086975b368e6522.png)

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.

---

<div class="post-metadata">

**Author:** ![brahimh](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/brahimh/32/37611_2.png) [@brahimh](https://community.n8n.io/u/brahimh)\
**Post date:** [September 22, 2025, 5:48pm UTC](https://community.n8n.io/t/executions-filter-by-trigger-or-trigger-node-name/138756/2 "2025-09-22T17:48:31Z")

</div>

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.