Test cases and pinning of output for triggering workflows

[Kheang]

I am running some tests using different MCP servers in order to compare the behaviors and results I get and I am using the data pinning in order to execute my tests without having to trigger them.

This is practical.
But the issue I end up noticing, is I always have to go edit my values in order to re-execute my workflow to record the different outcomes.

It would be a nice feature to have to be able to create data templates or test cases that could be run and executed without having to go manually edit each workflow’s pinned data.

For example, if I want to test multiple individual prompts and record their result.
I have to open the workflow, edit and then re-execute.

I know I can create a parent workflow and trigger the sub-workflows, but it would be a nice idea to be able to create a list of pinned data and select the one we want to execute?

How do you guys handle this on your end?

Thanks!

[Erick_Torres]

Pin Data (Fix Output), an existing official feature. Since recent versions, n8n allows you to pin the output of a node. This can be done using the “Pin Data” button on any node in the editor. This allows you to always reuse that output without re-executing the previous node. However, this has a limitation: It only affects the editor session and is manual; it does not work as dynamic input or as a “saved” version for other users.

For Test Cases, a community-requested feature: There is no formal native “test case” system in n8n yet. The current workaround:

• Use Set nodes to create mock data.
• Use the “Execute Node” option directly.
• Pin data manually.