Allow manual/test executions without saving the workflow first

Feature Requests
1

The idea is:

Allow manual/test executions (“Execute workflow” / “Execute step”) to run on the current, unsaved editor state of a workflow, without forcing the workflow to be saved first.

Earlier versions of n8n allowed this: you could tweak a node, run it, look at the output and discard the change. In recent versions a save is required before a manual execution can run.

Possible approaches:

  1. An “Execute without saving” option that sends the current editor workflow JSON with the run request (as older versions did).
  2. Run unsaved executions against an ephemeral/temporary workflow snapshot that is discarded afterwards, so the engine still has a reference to work with.
  3. An instance-level or workflow-level setting so admins can allow/disallow unsaved test runs per environment (some teams may want strict “save first” on prod, others need quick testing).

My use case:

We run n8n on staging and production instances. When debugging a live workflow, we often need a quick one-off test run with slightly changed parameters: testing an expression, trying different input values, checking what an API returns, etc.

Today, every one of those experiments forces a save of the workflow. On prod/staging that means modifying the stored workflow just to try something, then remembering to revert it afterwards.

I think it would be beneficial to add this because:

  • Safety: temporary test edits no longer have to be saved into production/staging workflows, reducing the risk of accidental changes going live.
  • Clean history: avoids polluting version history with throwaway “test” saves.
  • Faster debugging: restores the quick edit → run → inspect → discard loop that made iterating in n8n so fast.
  • Workarounds are poor: duplicating the workflow into a scratch copy is tedious and loses context (credentials, pinned data, surrounding nodes); saving then manually reverting is error-prone.

Any resources to support this?

I understand the execution engine needs a persistent workflow reference, but an opt-in path for temporary, non-persisted test runs would bring back an important debugging workflow.

1 Like