n8n Trigger Types: Webhook, Schedule, App Event & Manual Explained

A trigger node is the exclusive entry point for any automated workflow execution in n8n. It listens for a specific event—a webhook call, a scheduled time, an app event, or a manual click—and starts the workflow when that event occurs. Without a trigger, no automated workflow can run. Triggers are visually marked by an orange lightning bolt icon and have an output connector but no input connector. [1]

When should you use a manual trigger to run an n8n workflow?

Use a manual trigger when you need on‑demand execution—clicking the “Execute Workflow” button in the n8n canvas runs the workflow once. It requires no configuration and is the primary tool for building, testing, and debugging workflows before switching to an automated trigger for production use. [2]

Manual triggers also suit one‑off data migrations, temporary processing tasks, and approval workflows that require human judgment. You can configure manual triggers with input parameters, enabling users to supply variables before the workflow starts. For a deeper dive, see how sub‑workflows modularize automation.

How does a schedule trigger use cron expressions to automate n8n workflows?

A schedule trigger executes workflows at fixed intervals using cron syntax—a six‑field expression covering seconds, minutes, hours, day, month, and weekday. For example, 0 8 * * 1‑5 runs at 8 AM Monday through Friday. The Interval mode offers simpler recurring intervals like “every 30 minutes” without cron knowledge. [3]

Schedule triggers are resource‑efficient because n8n activates them only at the designated moment. For a full taxonomy of scheduled use cases, visit our n8n benefits and use cases.

What makes a webhook trigger start n8n workflows in real time?

A webhook trigger exposes a unique, auto‑generated URL that listens for incoming HTTP requests—typically POST. When any external service sends a request to that URL, n8n fires the workflow immediately. This push model delivers near‑zero latency, making webhook triggers the foundation of real‑time automations. [4]

The trigger generates both a Test URL (for local development) and a Production URL that works once the workflow is activated. You can set the HTTP method to GET or POST, configure a response mode (immediate, using a Respond to Webhook node, or wait for workflow completion), and secure the endpoint with HMAC signatures, Basic Auth, or Header Auth. For full hardening details, consult our n8n webhook authentication hardening guide.

How do app event triggers listen for changes in third‑party services?

App event triggers—such as the GitHub Trigger, Gmail Trigger, or Trello Trigger—listen natively for events inside a specific app service. These triggers use either webhooks or polling under the hood, but handle all the plumbing: authentication, subscription, data parsing, and error retries are pre‑built into the node. [1]

For example, a Trello Trigger node creates a Trello webhook that notifies n8n whenever a card moves or a comment is added—instead of n8n repeatedly polling the Trello API[reference:0]. App event triggers are the simplest way for teams who use a specific tool to build reliable event‑driven workflows around that tool. For a broader look at workflow patterns, see our n8n use cases guide.

How does a polling trigger check for new data on a set schedule?

A polling trigger repeatedly checks an external service at a fixed interval—every minute, every 5 minutes, or hourly—for new or changed data. It works even with APIs that lack webhook support. When n8n detects new records, the polling trigger starts the workflow and passes those records as the initial input. [5]

To avoid processing the same data twice, a polling trigger tracks the last checkpoint—typically a timestamp or highest record ID—so each interval only fetches items newer than that marker[reference:1]. Polling is less efficient than webhooks for high‑frequency use, but indispensable for services without push capabilities. For scaling considerations, refer to our n8n architecture and scaling guide.

When should you choose webhook versus polling triggers in n8n?

Choose webhook triggers when the external service supports push notifications—they deliver real‑time execution with zero wasted API calls. Use polling triggers when the service lacks webhook support or when you need to batch‑process data at slower intervals. Webhooks are push‑based and efficient; polling is pull‑based and can hit rate limits if the interval is too short. [6]

For many production workflows, the optimal pattern is a webhook trigger as the primary entry point backed by a polling fallback for services that cannot push. Learn how these trigger types integrate into larger automation systems in the n8n workflow automation platform guide.