How to run n8n workflows manually?

The simplest way to run an n8n workflow manually is to open the workflow in the editor and click the Execute Workflow button. This runs the workflow once, immediately, using whatever input data you currently have set in your nodes. This is how you manually test or manually trigger workflows that normally run on schedules, webhooks, or other triggers.

 

What “running manually” means in n8n

 

In n8n, workflows usually start with a trigger node (like Webhook Trigger, Cron Trigger, IMAP Trigger, etc.) which decides when the workflow runs. A manual run simply bypasses the usual trigger conditions and forces a one‑time execution. It does not affect production scheduling and it does not change how the workflow will run in the future. It’s just a way for you to test or run it immediately.

• A manual run only happens inside the editor UI.
• It uses the current version of the workflow (even if it’s not activated).
• It shows you real-time node-by-node results so you can debug.

 

How to run a workflow manually (in the UI)

 

This is the normal way most developers run things manually:

• Open the workflow in the n8n editor (cloud or self‑hosted).
• Look at the top-right area and find the Execute Workflow button.
• Click it. The workflow will start immediately.
• Watch nodes turn green as they execute; each node will show its output data.

If your workflow starts with a Webhook Trigger, you will see a special “Waiting for Webhook Call” message first. That means n8n is waiting for you to hit the test webhook URL manually. This still counts as a manual run.

 

Running specific nodes manually

 

You can manually run only some nodes instead of the full workflow, which is very practical in production debugging:

• Select a node.
• Click Execute Node.
• n8n will run just that node, using the existing input data shown on the left panel.

This helps you avoid re-running an entire workflow when you only want to test one API call or transformation node.

 

Manual execution via API (less common, but valid)

 

If you’re automating from outside n8n (e.g., triggering from a backend system or a script), you can trigger a workflow with the n8n REST API. This is still a “manual” run in the sense that you decide when it runs, but it's done programmatically.

You need the workflow to have an Execute Workflow Trigger or a Webhook Trigger to make this possible. For example, with a webhook trigger:

 

curl -X POST https://your-n8n-domain/webhook/test-endpoint \
  -H "Content-Type: application/json" \
  -d '{"hello": "world"}'

 

This triggers the workflow immediately using whatever data you send. This behaves the same as a manual execution from the UI once the webhook is called.

 

Common pitfalls when running manually

 

• Cron Triggers never run manually: they only run on schedule. You must click Execute Workflow for a manual start.
• Webhook Triggers need a real call: the workflow does not “just run” — you must hit the test URL.
• Node credentials must be valid: manual runs still require proper API keys, OAuth tokens, etc.
• Manual runs can time out: for long-running workflows (many minutes or hours), the editor session may disconnect. For very long processes, it's better to use queue mode or design smaller workflows.

 

Summary

 

To run an n8n workflow manually, open the workflow in the editor and click Execute Workflow. This forces a one-time run regardless of the trigger type and lets you inspect every node's output. You can also run individual nodes or trigger workflows manually using a webhook or API call. These approaches are standard, production-safe ways to test or control n8n workflows.