What is a manual trigger in n8n?
Quick answer
A manual trigger in n8n is a start node that fires only when you click Execute workflow in the editor. In the trigger list it is called Trigger manually, and on the canvas it shows as When clicking 'Execute workflow'. It is for building and testing, not for running on its own.
Last updated
Take the free module →Module 12 of the free AI for Operations Teams course, about 15 minutes. No account needed.
Updated · By Robert Breen
Why it matters for a small business
When I build something new, I don't want a form, a schedule or an inbox deciding when it runs. A manual trigger lets me press a button, watch every step and fix the one that breaks. Nothing outside the editor can set it off, so half-built work can't email a client by accident.
The catch is that it stays manual forever. Publishing a workflow whose only trigger is manual does not make it run by itself. Before going live you swap it for a real trigger, such as a schedule, a form or a new-email trigger, and then publish.
In a real lesson: n8n: Turn Meeting Notes into Action Items in a Google Sheet
In the meeting notes to action items lesson, the first click is Trigger manually, described as "Runs the flow on clicking a button in n8n." It lands on the canvas as When clicking 'Execute workflow' with nothing to set.
You then build the rest for Meridian Accounting Group, a made-up firm: read the notes sheet, ask OpenAI for tasks, split them and append rows. The last step points out that the workflow works but is not published and starts from a button. To run it after every meeting, you would swap in a form or new-row trigger, then Publish.
Try this lesson free or read the step-by-step guide.
How AI helps
A manual trigger is the safest place to test an AI step. I run the workflow by hand a few times on made-up notes, read what the model returned in each node, and tighten the prompt before any real data flows. Try it in the meeting notes lesson, then ask ChatGPT which trigger fits your real starting event.
Common confusions
Manual trigger vs Execute workflow
The manual trigger is the start node. Execute workflow is the button that fires it. Execute workflow also tests workflows that start with other triggers, using test or pinned data.
Manual trigger vs a published workflow
Publishing hands the workflow to its triggers. A manual trigger has nothing to listen for, so it still waits for your click.
Tips
- Start new builds with a manual trigger, then replace it once every step works.
- Error workflows don't run for manual runs, so test alerts with a real trigger.
Related terms
More n8n and automation terms
Where you use it: free lessons
- n8n: Turn Meeting Notes into Action Items in a Google Sheet (n8n, 15 min)
- Meeting to Action: Recap, Tracker Rows and a Kickoff Deck (ChatGPT, n8n, Gamma) (n8n, 14 min)
- n8n: What Is n8n? Build Your First Workflow (n8n, 8 min)
- n8n: Items, JSON and Expressions, Explained by Doing (n8n, 9 min)
Frequently asked questions
- What does Trigger manually mean in n8n?
- It means the workflow starts only when you click Execute workflow in the editor. Nothing else can start it.
- Can I publish a workflow with a manual trigger?
- A manual trigger never fires on its own, even when published. Add or swap in a schedule, webhook, form or app trigger for real runs.
- What is "When clicking Execute workflow" in n8n?
- It is the canvas name of the manual trigger node. It fires each time you click Execute workflow.