Let's Shape The Future Of Your Investments!
Natoque iaculis cursus augue urna commodo aptent morbi tortor porttitor quis ornare.
n8n Trigger Nodes: Types, Activation, and Execution Modes
Choose a trigger by how work enters n8n.
Short answer: Use a webhook for an incoming request, a schedule for a time, an app event for a supported change, polling when no event exists, and a manual trigger for testing.
What does a trigger node do in n8n?
A trigger starts a workflow. It defines when the first execution begins. The trigger may wait for a request, watch an app, check a schedule, or wait for you to click Execute.
The trigger does not complete the workflow. It only supplies the first event or data. Later nodes validate the input, transform it, and perform the action.
When should you use a manual trigger?
Use a manual trigger while building or testing a workflow. It starts when you select Execute Workflow in the editor.
This is useful for sample data, one-time jobs, and controlled tests. It is not a production schedule. Move to an automated trigger after the node path works with real input.
n8n manual trigger documentation
When should you use a schedule trigger?
Use a schedule trigger when time is the event. Common examples include a daily report, a five-minute check, or a weekly cleanup.
Set the interval and timezone together. A correct cron expression can still run at the wrong local time if the workflow timezone is wrong. Test the next run before relying on it.
n8n schedule trigger documentation
When should you use a webhook trigger?
Use a webhook when another system can call n8n. The sender makes an HTTP request to the webhook URL. n8n then starts the workflow.
Webhooks fit form submissions, payment notices, and application events. Check authentication, request method, response behavior, and replay handling before using one in production.
n8n webhook trigger documentation
When should you use an app event trigger?
Use an app event when the integration exposes the change you need. Examples include a new row, a new message, or a changed record.
Check the event name and delivery model. Some integrations deliver events immediately. Others use polling behind the interface. The distinction affects delay and request volume.
When is polling the better option?
Use polling when the service has no usable webhook or event trigger. n8n checks the service on a schedule and looks for new or changed data.
Polling needs a stable cursor or timestamp. Without one, the workflow may repeat old records or miss changes. Record the last successful check when the source supports it.
How do you choose between trigger types?
| Trigger | Best fit | Check first |
|---|---|---|
| Manual | Testing and one-time runs | Sample input and repeatability |
| Schedule | Time-based work | Timezone, interval, and overlap |
| Webhook | Incoming requests | Auth, retries, and response status |
| App event | Supported changes in an app | Event coverage and delivery delay |
| Polling | Sources without events | Cursor, rate limits, and duplicates |
What should you test before activation?
- Send one known input or run the trigger manually.
- Confirm the first node receives the expected fields.
- Check timezone and duplicate behavior.
- Test an empty response and a failed request.
- Review the execution log before activating the workflow.
For the larger workflow structure, see triggers, branches, and sub-workflows. For a side-by-side trigger choice, see webhook, schedule, app event, and manual triggers.