feat(editor): Filter Executions by executed node #16036

Alexandero89 · 2025-06-05T00:52:40Z

Introduced the ability to filter executions by specific nodes in both backend and frontend components.

Summary

This PR is a first draft and also serves as a Request for Comments (RFC).

I frequently need to see all executions where a specific node was executed.
Currently, there is no way to filter executions by executed nodes.
This PR adds a button to the right-click context menu in the editor, enabling quick access to this functionality.
It introduces an update to the /executions route router, so that it can accept a URL parameter.
The URL parameter allows specifying the nodeId to be filtered for in the backend/database.

Feedback and suggestions are highly appreciated!

Showcasevideo

bildschirmaufzeichnung-vom-2025-06-05-02-47-12_wKow5MCV.mp4

Review / Merge checklist

PR title and summary are descriptive. (conventions)
Docs updated or follow-up ticket created.
Tests included.
PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

Introduced the ability to filter executions by specific nodes in both backend and frontend components.

CLAassistant · 2025-06-05T00:52:46Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Alexandero89
❌ Alex O

Alex O seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

cubic-dev-ai

cubic found 10 issues across 12 files. Review them in cubic.dev

_{React with 👍 or 👎 to teach cubic. Tag @cubic-dev-ai to give specific feedback.}

cubic-dev-ai · 2025-06-05T00:57:14Z

packages/frontend/@n8n/i18n/src/locales/en.json

 	"contextMenu.addSticky": "Add sticky note",
 	"contextMenu.editSticky": "Edit sticky note",
 	"contextMenu.changeColor": "Change color",
+	"contextMenu.FilterExecutionsBy": "Filter Executions by",


Translation key naming inconsistency. The key uses camelCase 'FilterExecutionsBy' but is referenced in code as 'filter_executions_by'.

Suggested change

"contextMenu.FilterExecutionsBy": "Filter Executions by",

"contextMenu.filter_executions_by": "Filter Executions by",

Will change this and some other variables to be consistent with the rest of the naming

cubic-dev-ai · 2025-06-05T00:57:14Z

packages/frontend/editor-ui/src/views/WorkflowExecutionsView.vue

 		: [],
 );

+const FilterExecutionsBy = computed(() => {


Rule violated: Ensure every PR has unit tests for Vue files

Missing unit tests for WorkflowExecutionsView.vue component

cubic-dev-ai · 2025-06-05T00:57:14Z

packages/@n8n/db/src/repositories/execution.repository.ts

+			const idConditions: string[] = [];
+			query.nodesExecuted.forEach((node, idx) => {
+				idConditions.push(
+					`json_type(json_extract(execution_data.data, '$[4].' || :nodeName${idx})) IS NOT NULL`,


SQL function json_extract may not be compatible with all database types

Is this query executed in the sqlite and the postgres setup aswell?
Or only the sqlite?

Cause:
"json_extract is natively supported in modern SQLite versions (3.9.0 and above, released since 2015) if it is compiled with the JSON1 extension—most pre-built binaries include this by default."

The query is executed in postgres set up as well. Can you change the way the execution data is extracted?

updated the query to also support postgresdb

cubic-dev-ai · 2025-06-05T00:57:14Z

packages/@n8n/db/src/repositories/execution.repository.ts

+			const idConditions: string[] = [];
+			query.nodesExecuted.forEach((node, idx) => {
+				idConditions.push(
+					`json_type(json_extract(execution_data.data, '$[4].' || :nodeName${idx})) IS NOT NULL`,


Hardcoded array index '$[4]' in JSON path is brittle and lacks documentation

I analyzed the json in the database and it seems the 4th element is a list where all executed nodes of an execution are listed. so we should always find the node we are searching for in the 4th element.

The hardcoded index is brittle, indeed. @Alexandero89 have you found any other way to do this?

actually it seems this is some kind of standard. The executed nodes are always saved at position 4.
I think someone of your team at n8n should know if this is a standard and if its always saved at this position or if we can do this in some better way.

cubic-dev-ai · 2025-06-05T00:57:14Z

packages/frontend/editor-ui/src/Interface.ts

 	startedBefore?: string;
 	annotationTags?: string[];
 	vote?: ExecutionFilterVote;
+	nodesExecuted: string[];


Type inconsistency between ExecutionFilterType and ExecutionsQueryFilter interfaces. In ExecutionFilterType, nodesExecuted is optional, but in ExecutionsQueryFilter, it's required. This could cause runtime errors when transforming between these types in executionFilterToQueryFilter function.

Suggested change

nodesExecuted: string[];

+ nodesExecuted?: string[];

cubic-dev-ai · 2025-06-05T00:57:14Z

packages/frontend/editor-ui/src/components/canvas/Canvas.vue

 import Edge from './elements/edges/CanvasEdge.vue';
 import Node from './elements/nodes/CanvasNode.vue';
 import { useViewportAutoAdjust } from '@/components/canvas/composables/useViewportAutoAdjust';
+import { useRouter, useRoute } from 'vue-router';


Rule violated: Ensure every PR has unit tests for Vue files

Missing unit tests for the new filter executions functionality

cubic-dev-ai · 2025-06-05T00:57:15Z

packages/frontend/editor-ui/src/components/canvas/Canvas.vue

+async function onFilterExecutionBy(input: { ids: string[] }) {
+	const workflowId = route.params.name as string;
+	if (!workflowId || !input || !input.ids || input.ids.length === 0) return;
+	const customFilter = nodeDataById.value[input.ids[0]]?.name;


Missing validation for nodeDataById.value[input.ids[0]] existence before accessing name property

Suggested change

const customFilter = nodeDataById.value[input.ids[0]]?.name;

+ const customFilter = nodeDataById.value[input.ids[0]]?.name || undefined;

cubic-dev-ai · 2025-06-05T00:57:15Z

packages/@n8n/db/src/repositories/execution.repository.ts

 		const qb = this.createQueryBuilder('execution')
 			.select(fields)
 			.innerJoin('execution.workflow', 'workflow')
+			// Add join to execution_data in the query builder


Comment indicates this join might not be needed for all queries, but it's added unconditionally

I will have to think about how to solve this better. not every execution needs this join.
feedback is very welcomed here

implemented a better solution in the new commit. have a look

cubic-dev-ai · 2025-06-05T00:57:15Z

packages/frontend/editor-ui/src/types/canvas.ts

 		payload?: CanvasNodeEventBusEvents[keyof CanvasNodeEventBusEvents];
 	};
 	tidyUp: { source: CanvasLayoutSource };
+	filter_executions_by: { ids: string[] };


The event only uses the first node ID from the array in the implementation, but the type suggests multiple IDs are supported.

For this proof of concept i implemented the filtering for only one node.
The idea is later to be able to filter by multiple nodes that are marked.

Let's start with one node 👍

cubic-dev-ai · 2025-06-05T00:57:15Z

packages/frontend/editor-ui/src/components/canvas/Canvas.vue

 		case 'extract_sub_workflow':
 			return emit('extract-workflow', nodeIds);
+		case 'filter_executions_by':
+			onFilterExecutionBy({ ids: nodeIds });


Redundant function call before emitting the same event

Joffcom · 2025-06-05T01:00:32Z

Hey @Alexandero89,

Thanks for the PR, We have created "GHC-2353" as the internal reference to get this reviewed.

One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team.

bundlemon · 2025-06-19T08:06:18Z

BundleMon

Unchanged files (2)

Status	Path	Size	Limits
✅	WASM Dependencies _{tree-sitter-bash.wasm}	181.26KB	-
✅	WASM Dependencies _{tree-sitter.wasm}	74.47KB	-

No change in files bundle size

Groups updated (2)

Status	Path	Size	Limits
✅	*/.js	5.16MB (+27.53KB +0.52%)	-
✅	*/.css	182.67KB (+3.62KB +2.02%)	-

Final result: ✅

View report in BundleMon website ➡️

Current branch size history | Target branch size history

packages/frontend/@n8n/i18n/src/locales/en.json

nikhilkuria · 2025-07-07T15:24:55Z

packages/@n8n/db/src/repositories/execution.repository.ts

+			.innerJoin('execution.workflow', 'workflow');
+
+		// Add join to execution_data only if nodesExecuted is not null or not an empty array
+		if (nodesExecuted && Array.isArray(nodesExecuted) ? nodesExecuted.length > 0 : true) {


Won't this always be true?
If nodesExecuted is undefined?, then true is returned,
If it's an array, nodesExecuted.length > 0 is returned which is also true

You are right. Changed the check to be more precise

nikhilkuria

Really nice idea @Alexandero89 👏
Let's polish it and make it better

nikhilkuria · 2025-07-07T15:26:03Z

Also, can you fix the broken tests?

changing label

better check for nodesExecuted not to be empty

better db query to also support postgresdb

void the promise instead of ignoring it

nikhilkuria · 2025-08-05T11:03:42Z

packages/@n8n/db/src/repositories/execution.repository.ts

+		if (query.nodesExecuted && query.nodesExecuted.length > 0) {
+			const idConditions: string[] = [];
+			query.nodesExecuted.forEach((node, idx) => {
+				const fragment = isPostgres


Did you get the changes to work in a postgresdb?
I had to change it as follows for the filtering to work

const fragment = isPostgres ? `jsonb_exists(execution_data.data::jsonb->4, :nodeName${idx})` : `json_type(json_extract(execution_data.data, '$[4].' || :nodeName${idx})) IS NOT NULL`;

Is this related to different postgres versions?

nikhilkuria · 2025-08-05T11:09:17Z

I think it's shaping real nice. The check for postgres is the way to go. Nice work!

nikhilkuria · 2025-08-05T11:09:32Z

Can you also take a look here, please?
https://www.loom.com/share/296342209a5e48c88847d73a97dbde26?sid=3025ded6-8d43-4ffe-8876-f15cc997a4f5

nikhilkuria · 2025-09-19T09:40:06Z

Hi @Alexandero89 did you manage to take a look at my last comments

nikhilkuria · 2025-10-05T09:28:19Z

@Alexandero89 we are closing this PR. When you find time to work on, please reopen and we can continue our conversation

Alex O added 2 commits June 5, 2025 02:24

feat(executions): add filter by executed nodes

9e58acc

Introduced the ability to filter executions by specific nodes in both backend and frontend components.

fix typo

124815d

fix typo

f2ca467

cubic-dev-ai bot reviewed Jun 5, 2025

View reviewed changes

n8n-assistant bot added community Authored by a community member core Enhancement outside /nodes-base and /editor-ui in linear Issue or PR has been created in Linear for internal review labels Jun 5, 2025

Alex O and others added 5 commits June 5, 2025 14:53

Better db querying and only innerjoin when necessary

a3bf3eb

follow naming convention

504be33

make filter value optional

2046478

just some optimization

4cbf7ba

Merge branch 'master' into custom_filter_rebased

252e254

nikhilkuria reviewed Jul 7, 2025

View reviewed changes

packages/frontend/@n8n/i18n/src/locales/en.json Outdated Show resolved Hide resolved

nikhilkuria reviewed Jul 7, 2025

View reviewed changes

nikhilkuria requested changes Jul 7, 2025

View reviewed changes

Alexandero89 added 4 commits July 7, 2025 20:24

Update en.json

570f1d0

changing label

Update execution.repository.ts

56e068c

better check for nodesExecuted not to be empty

Update execution.repository.ts

36a03e5

better db query to also support postgresdb

Merge branch 'master' into custom_filter_rebased

4ee043d

Alexandero89 changed the title ~~Filter Executions by executed node~~ fix(editor): Filter Executions by executed node Jul 7, 2025

Alexandero89 changed the title ~~fix(editor): Filter Executions by executed node~~ feat(editor): Filter Executions by executed node Jul 7, 2025

Update Canvas.vue

cdbefa1

void the promise instead of ignoring it

nikhilkuria reviewed Aug 5, 2025

View reviewed changes

nikhilkuria closed this Oct 5, 2025

	"contextMenu.FilterExecutionsBy": "Filter Executions by",
	"contextMenu.filter_executions_by": "Filter Executions by",

	const customFilter = nodeDataById.value[input.ids[0]]?.name;
	+ const customFilter = nodeDataById.value[input.ids[0]]?.name \|\| undefined;

feat(editor): Filter Executions by executed node #16036

feat(editor): Filter Executions by executed node #16036

Uh oh!

Conversation

Alexandero89 commented Jun 5, 2025

Summary

Showcasevideo

Review / Merge checklist

Uh oh!

CLAassistant commented Jun 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Alexandero89 Jun 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cubic-dev-ai bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

Joffcom commented Jun 5, 2025

Uh oh!

bundlemon bot commented Jun 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

BundleMon

CLAassistant commented Jun 5, 2025 •

edited

Loading

Alexandero89 Jun 5, 2025 •

edited

Loading

bundlemon bot commented Jun 19, 2025 •

edited

Loading

nikhilkuria Aug 5, 2025 •

edited

Loading