Trigger Types in n8n: Schedule, Webhook, Polling, Manual, Chat

Every n8n workflow needs a starting point, otherwise simply nothing happens. This starting point is called a trigger, and n8n offers significantly more than just "Schedule" or "Webhook" for this. From time-based automation through incoming HTTP calls to the chat interface for AI agents: which trigger type fits your scenario directly determines how reliably and how quickly your workflow reacts.

This overview shows you the most important trigger types in n8n, how they work technically, and when to use which one. The source is the official n8n documentation on trigger nodes.

What is a trigger in n8n anyway?

According to the documentation, a trigger node is a node that starts a workflow in response to a certain condition. Every production workflow needs at least one trigger so that n8n knows when it should run at all.

A workflow can indeed contain several triggers at the same time, for example a Schedule Trigger for the daily routine and additionally a webhook for spontaneous external prompts. With each individual execution, however, only the trigger whose condition has actually occurred fires. So you retain control over the reason your workflow runs each time, even if several paths lead there.

Schedule Trigger: time-based automation

The Schedule Trigger starts workflows at fixed times and intervals, similar to the Unix cron utility. According to the documentation on the Schedule Trigger node, several interval modes are available to you:

• Seconds and Minutes: fixed intervals, for example every 30 seconds or every 5 minutes.
• Hours: an interval in hours plus the exact minute within the hour.
• Days: an interval in days plus a time, for example every 2 days at 9:15 AM.
• Weeks: a weekly interval, weekday and time, for example every Monday at 3:30 PM.
• Months: a monthly interval, day of the month and time.
• Custom (Cron Expression): a freely defined cron syntax for more complex schedules, for example `0 9 * * 1-5` for weekdays at 9:00 AM.

Important to know: The Schedule Trigger only takes effect when the workflow is published, and it follows either the workflow's or the n8n instance's time zone. You can also combine several trigger rules within a single Schedule Trigger if a workflow should run at different times with different frequency.

Recommended use: The Schedule Trigger fits whenever you are automating a fixed routine, for example nightly data synchronizations, weekly reports or regular cleanup tasks like execution pruning checks. It is the right choice when no one triggers an event from outside, but the clock sets the pace.

Webhook Trigger: reacting to external events

The Webhook node connects external services with n8n by waiting for incoming HTTP calls and starting the workflow immediately when one arrives. According to the documentation on the Webhook node, it supports the methods GET, POST, PUT, PATCH, DELETE and HEAD, with a maximum payload size of 16 MB per call.

Particularly relevant in practice is the distinction between two URLs:

• Test URL: active as soon as you click "Listen for Test Event" in the editor. You see incoming data directly in the interface.
• Production URL: only becomes active once the workflow is published. Incoming calls do not appear live in the editor, but can be tracked in the "Executions" tab.

For security, Basic Auth, Header Auth and JWT Auth are available, along with IP whitelisting, ignoring bots and CORS settings. For the response, you can choose between an immediate acknowledgment, the response after the last node has completed, a custom response via a separate Respond to Webhook node, or a streaming response.

Recommended use: Use the Webhook Trigger when another system should actively report something to n8n, for example a new form submission, a payment confirmation from a payment provider, or an event from a CRM. The big advantage over the Schedule Trigger is response time: the workflow starts practically the moment the event occurs, instead of only at the next scheduled run.

Polling Trigger: checking instead of being notified

Not every service can trigger a webhook itself. Many external systems, such as classic email inboxes or RSS feeds, do not offer active notifications. For this case there are Polling Triggers: they themselves check at a fixed rhythm whether there is something new, and only start the workflow when something has actually changed.

A good example of this is the RSS Feed Trigger. According to the documentation on the RSS Feed Trigger node, this node queries the configured feed URL at a configurable rhythm and only triggers the workflow for new entries. Among other options, hourly, daily, weekly and monthly check intervals are available, as well as free cron expressions for individual schedules. Other n8n nodes are based on the same principle, such as the Email Trigger via IMAP or the Local File Trigger, which detect new messages or new files respectively through regular checking.

Recommended use: Polling is the right choice when the source itself does not offer push notifications, but you still want to process the event in a timely manner. Keep in mind that too tight a check interval creates unnecessarily many executions and thus also unnecessary API calls, while too wide an interval extends the response time. A sensible middle ground depends on how often the source actually changes.

Manual Trigger: controlled starting by click

The Manual Trigger starts a workflow exclusively when you actively click "Execute Workflow" in the editor. According to the documentation on the Manual Trigger node, it is particularly suited for two situations: testing a workflow before you add an automatic trigger, and for workflows that are deliberately not meant to run automatically because a human wants to specifically trigger each run.

There is a technical limitation you should know about: only a single Manual Trigger node is ever allowed per workflow.

Recommended use: Use the Manual Trigger during the development phase to test a workflow step by step, or for rare, deliberately manually triggered processes such as one-off data migrations. For continuous production operation, however, it is unsuitable, because no one should have to permanently click "Execute" there.

Chat Trigger: entry point for AI chatbots

The Chat Trigger is used to build AI workflows for chatbots and other chat interfaces. According to the documentation on the Chat Trigger node, it must be connected to an Agent or Chain root node so that the conversation is actually answered. Each individual message in a conversation triggers a complete workflow execution, which you need to take into account when planning your execution quota: a chat with ten messages consumes ten executions.

For access, the node offers two modes: the Hosted Chat with a ready-made n8n interface, and the Embedded Chat, which you integrate into your own application via the webhook URL. For security, no authentication, Basic Auth, or n8n's own user authentication are available. For the response modes, you can choose between completion after the last node, individual response nodes, and a streaming response for real-time output.

Recommended use: The Chat Trigger fits as soon as people should communicate directly with an AI agent in n8n, for example for an internal support bot, a knowledge assistant based on your own documents, or a chat interface embedded on a website.

Choosing the trigger type by scenario

As a rough guide for practice:

• Fixed points in time or intervals: Schedule Trigger.
• Another system should actively report something: Webhook Trigger.
• The source does not offer push notifications: Polling Trigger, for example RSS Feed Trigger or Email Trigger via IMAP.
• Testing or a deliberately manually controlled process: Manual Trigger.
• Direct dialogue with an AI agent: Chat Trigger.

In practice, you often combine these types within one automation concept: a webhook for the spontaneous request, a Schedule Trigger for the daily follow-up check, a Manual Trigger for tests during development. If you are unsure about the selection or the clean configuration of your triggers, NordFlux supports you with the setup and security of n8n workflows, including a suitable trigger strategy for your scenario.

Frequently Asked Questions

Can a workflow have several triggers at the same time?

Yes, a workflow can contain several trigger nodes, for example a Schedule Trigger and additionally a webhook. With each execution, however, only the trigger whose condition has actually occurred fires, the others remain inactive at that moment.

What is the difference between the Webhook Trigger and the Polling Trigger?

The Webhook Trigger passively waits for incoming calls and reacts virtually in real time as soon as an external system actively contacts it. The Polling Trigger, on the other hand, itself checks with the source at a fixed rhythm whether there is anything new, which is particularly suitable for services that do not offer their own push notifications.

Does the workflow need to be published for the Schedule Trigger to work?

Yes, according to the documentation, the Schedule Trigger only takes effect for a published workflow. Changes to the stored cron variables also only take effect after republishing.

What is the Manual Trigger suited for in production operation?

The Manual Trigger is primarily intended for tests and deliberately manually controlled processes, such as one-off data migrations. It is unsuitable for continuously running, automated processes, because no one should have to click "Execute" manually on a regular basis there.

How many executions does a Chat Trigger workflow consume?

Each individual message within a conversation triggers a complete workflow execution. A conversation with ten messages therefore corresponds to ten separate executions, which you should take into account when planning your execution quota.