Types of Triggers in n8n

Every automation needs a starting point. In n8n, that starting point is handled by Trigger nodes. A trigger defines when your workflow should begin, whether it’s time-based, event-based, or even manual.

In this article, we’ll cover the 6 main types of triggers in n8n, along with what, why, when, and how to use them, plus real-world examples.

What Are Triggers in n8n?

Triggers are special nodes that start your workflow automatically (or manually). Without them, n8n won’t know when to run your automation.

For example

A Cron Trigger runs a workflow every morning at 9 AM.
A Webhook Trigger starts instantly when someone submits a form.
A Manual Trigger is used to test workflows while building them.

Why Use Triggers?

⏰ Automation without effort → Workflows run without manual intervention.
⚡ Instant reactions → Respond to events in real time.
📊 Consistency → No missed schedules or human errors.
🔄 Scalability → Handle repetitive tasks at scale.

The 6 Types of Triggers in n8n

1. Manual Trigger

The most basic trigger.
You start the workflow manually from the editor.
Mainly used for testing and debugging.

💡 Example Use Cases:

Test a new workflow before connecting real data.
Run a one-time data migration.

2. Time-Based Trigger (Cron)

Like a scheduler or alarm clock.
Runs workflows at fixed intervals or specific times.

💡 Example Use Cases:

Send daily reports at 9 AM.
Run weekly backups every Sunday at midnight.

3. Webhook Trigger (Event-based)

Creates a URL endpoint that listens for incoming requests.
Fires instantly when data is sent to the webhook.

💡 Example Use Cases:

Capture leads from a website form.
Get notified when a payment succeeds.

4. App-Specific Triggers

Triggers are built into specific integrations.
Fires when an event occurs within the app.

💡 Examples:

Gmail Trigger → New email received.
Google Sheets Trigger → New row added.
Slack Trigger → New message posted.

5. Polling Trigger

Checks an app/API at intervals (if webhooks aren’t available).
Less “instant” than webhooks, but still useful.

💡 Example Use Cases:

Check Shopify every 10 minutes for new orders.
Poll an RSS feed for new blog posts.

6. Custom Event Trigger

Advanced triggers for special scenarios.
Can be created using:
- Custom Node development (TypeScript).
- Message queues/event streams (Kafka, RabbitMQ).
- Function Node logic to simulate conditions.

💡 Example Use Cases:

Start workflow when a Kafka event is published.
Trigger only if an order value > $1000.

Key Differences Between Trigger Types

Trigger Type	How It Works	Best For	Example Use Case
Manual	Run manually from the editor	Testing, one-time tasks	Debugging a new workflow
Time-Based (Cron)	Runs at fixed times/intervals	Scheduled automations	Daily reports at 9 AM
Webhook	Starts when an external request hits a URL	Real-time event automation	Website form submission → CRM
App-Specific	Fires when something happens in an app	App-to-app integrations	New Gmail email → Slack alert
Polling	Checks an API/service periodically	Apps without webhooks	Check Shopify orders every 10 min
Custom Event	User-defined/custom logic or event streams	Advanced scenarios	Kafka event → Data pipeline

Conclusion

Triggers are the foundation of every workflow in n8n. By understanding all 6 types: Manual, Time-Based (Cron), Webhook, App-Specific, Polling, and Custom Event Triggers, you can design automations that are both flexible and reliable.

Start with simple ones like Manual or Cron, then explore advanced triggers like Custom Event as your automations grow.

With the right trigger, your workflow always starts at the right moment