This article contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you.
n8n Workflow Triggers: How to Start Any Automation Automatically
Every n8n workflow starts with a trigger — the node that decides when your automation runs. Without the right trigger, nothing happens. With it, you can run workflows on a schedule, react to incoming data in real time, or respond to events inside your favourite apps. This guide walks you through each trigger type, step by step, so you can stop clicking "Execute Workflow" manually and let n8n do the work for you.
If you haven't set up n8n yet, you can get started with n8n — it offers 400+ integrations and lets you self-host for free or jump straight into n8n Cloud without any server setup.
What Is a Trigger Node in n8n?
A trigger node is always the first node in a workflow. It listens for a specific condition and fires the rest of the workflow the moment that condition is met. n8n supports three main categories of trigger:
- Schedule Trigger — runs your workflow at fixed times or intervals
- Webhook Trigger — fires when an external system sends an HTTP request to a unique URL
- App Event Trigger — listens for events inside connected apps (e.g. "new row in Google Sheets" or "new email in Gmail")
1. Schedule Trigger — Run Workflows on a Timer
When to use it
Use the Schedule Trigger when you need something to happen at a predictable time: a daily report, an hourly data sync, or a weekly digest email.
How to set it up
- Open a new workflow in n8n and click the + button to add the first node.
- Search for Schedule Trigger and select it.
- Choose your interval mode: Every X minutes/hours, Daily, Weekly, Monthly, or Custom (Cron).
- For custom schedules, enter a cron expression — for example,
0 8 * * 1-5runs the workflow every weekday at 08:00. - Click Save and then Activate the workflow (the toggle in the top-right corner). That's it — n8n will now fire the workflow automatically at your chosen time.
Pro tip
Always activate the workflow after saving. A saved but inactive workflow will never run on schedule — the activation toggle is what switches n8n from "test mode" to "live mode".
2. Webhook Trigger — React to Incoming HTTP Requests
When to use it
Use a Webhook Trigger when an external tool or service needs to push data to n8n the moment something happens — a new form submission, a Stripe payment, a GitHub push, or any other event that can send an HTTP POST or GET request.
How to set it up
- Add a Webhook node as the first node in your workflow.
- Choose the HTTP method: GET for simple triggers, POST for data payloads (most common).
- n8n generates a unique webhook URL — copy it.
- Paste that URL into the external service (e.g. in a Typeform "webhook" setting or a Stripe webhook endpoint).
- Click Listen for Test Event in n8n, then trigger the event in the external tool. n8n catches the payload and shows you the data structure.
- Build the rest of your workflow using that incoming data, then activate.
Test URL vs. Production URL
n8n provides two webhook URLs: a test URL (only active while you click "Listen for Test Event") and a production URL (active whenever the workflow is activated). Always switch to the production URL in your external service before going live.
3. App Event Trigger — Listen for Events Inside Connected Apps
When to use it
Many n8n nodes come with built-in trigger versions — for example Google Sheets Trigger, Gmail Trigger, Airtable Trigger, or Slack Trigger. These use either polling (n8n checks the app every minute) or real-time push (the app notifies n8n instantly via webhook).
How to set it up
- Add the app's trigger node — for example, search for Google Sheets Trigger.
- Connect your account via OAuth or API key.
- Select the event type: e.g. Row Added, Row Updated.
- Choose the spreadsheet and sheet you want to watch.
- Click Fetch Test Event to pull in a sample row and confirm the data looks right.
- Build the rest of your workflow, then activate.
Polling vs. instant triggers
If a trigger node uses polling, there will be a short delay (typically 1 minute) between the event happening in the app and n8n reacting. Webhook-based app triggers are near-instant. Check the node's documentation tab in n8n to see which method it uses.
4. Manual Trigger — For Testing Only
New workflows start with a Manual Trigger by default. It's useful for building and testing, but it requires you to click "Execute Workflow" every time. Replace it with one of the automatic triggers above before you activate a workflow for production use.
Combining Multiple Triggers in One Workflow
n8n allows you to add more than one trigger to the same workflow. For example, you might want a workflow to run both on a daily schedule and whenever a webhook fires. Simply add a second trigger node at the top level — both will feed into the same downstream nodes independently.
Common Mistakes to Avoid
- Forgetting to activate — saving a workflow does not activate it. Always flip the activation toggle.
- Using the test webhook URL in production — the test URL only works while you're actively listening. Use the production URL for live integrations.
- Not handling empty payloads — add an IF node after the trigger to check that the expected data exists before running further steps.
- Choosing polling when you need speed — if a 1-minute delay is too slow, look for a webhook-based trigger or use the Webhook node with the external service.
Next Steps
Once your trigger is in place, the rest of the workflow is about transforming and routing that data — using nodes like Set, IF, HTTP Request, and your chosen app integrations. The trigger is the foundation; everything else builds on top of it.
If you want to build and automate your own workflows without writing code, you can get started via n8n — including 400+ integrations and a free self-hosting option — to run any automation on your own schedule.