Three triggers: Manual / Schedule / Event

Why the three trigger types matter

Up to Chapter 8 you have built a workflow of "Schedule Trigger + Google Calendar + Slack", and from Chapter 9 you know how data moves from node to node. But stop and think for a second: when does a workflow actually start running?

• Only when you press the Execute Workflow button?
• Or automatically at 8:00 every day?
• Or the moment a particular Gmail arrives, or a particular URL is called?

Those three answers map onto n8n's three families of Trigger node — every workflow has to pick one at the front (with no Trigger node, n8n has no idea when it is supposed to do the work for you). Picking the wrong one costs you directly: you wanted a daily run but dropped in a Manual Trigger, and "why did nothing happen?" only surfaces a week later. This chapter lays all three types out in front of you so you pick right the first time.

All three trigger families at a glance

The "On app event" and "On a schedule" groups in the n8n nodes panel hold dozens of Trigger nodes, but underneath they are variations on three types:

The three types can coexist in one workflow — section 6 below shows how a single workflow carries Schedule and Manual at once, so it runs by itself during the day and you can still click it manually when you need to.

Manual Trigger: your best friend while building

Manual Trigger is the simplest of all the triggers — it has no parameters at all, it is one node sitting there. One sentence covers how to use it: press Execute Workflow at the top right and the workflow runs once from the start.

When to use it

• While building or testing: you have wired the workflow up and want to see the result now, and Manual is the fastest way. Click, look at the result, change a node, click again.
• One-off jobs: for example "export the full customer list for this month" — for a batch job you run once, setting up a Schedule is more trouble than it is worth; one click on Manual is enough.
• Flows that need a human gate: for example "the report only goes out after the manager has checked it". Where a person has to make the call, Manual Trigger turns pressing the button into an approval step.

When not to use it

• The workflow is live and has to run around the clock: Manual is a disaster here, because it never runs unless you press it. Once a workflow is live, the main trigger should become Schedule or Webhook.
• An outside system has to call in (for example a LINE bot receiving a message): Manual cannot do this at all, you need Webhook / an Event Trigger.

Schedule Trigger: runs on a clock, like cron

Schedule Trigger is the trigger automation uses most — you set a time rule and n8n runs the workflow for you when that time comes around. Typical uses: push the calendar to Slack at 8:00 in the morning, sync a database once an hour, send the weekly report at 9:00 every Monday.

The ways you can set Trigger Interval

The two setups you will use most

Run at 8:00 every morning: set Trigger Interval to Days, Days Between Triggers to 1, Trigger at Hour to 8, Trigger at Minute to 0.

Run at 9:30 Monday to Friday: set Trigger Interval to Weeks, Weeks Between Triggers to 1, tick Mon/Tue/Wed/Thu/Fri under Trigger on Weekdays, Trigger at Hour 9, Trigger at Minute 30. Or go straight to Custom (Cron) and enter 0 30 9 * * 1-5 (six fields: second minute hour day month weekday), one line and you are done.

How to set the timezone for a schedule

There are two levels of timezone setting, and one overrides the other. Note: the English edition uses Europe/London only as an example; replace it with the IANA timezone for your location. Knowing which level you are editing is what saves you half a day of confusion:

Precedence: workflow level > instance level > the documented America/New_York default. Which means:

1. Check the instance timezone instead of assuming it

   Ask the administrator whether GENERIC_TIMEZONE is set to an appropriate value such as Europe/London. Build a test workflow, run it every minute, and check whether the times on the Executions page match the intended local time. If they do, the instance default is suitable; an explicit workflow timezone is still safer when portability matters.

2. If they are wrong, set the workflow level

   Open the workflow's three-dot menu at the top right → Settings → there is a Timezone dropdown in the middle; pick your IANA timezone, for example Europe/London. Save when you are done.

3. Check every workflow that has a Schedule Trigger

   Workflow-level settings are independent of each other: even with workflow A set, a new workflow B has to be set again (if the instance level is UTC).

Event triggers: they run when something happens outside

Event triggers are the family that feels most like magic: you are not the one acting, the outside world is. Someone fills in a form, mail arrives, a Sheet is edited, someone pushes to GitHub — when those things happen, n8n runs on its own. The Event Trigger nodes you will use most:

Webhook is the king of event triggers: it takes anything that can call in over HTTP — that is what all of Chapter 22 is about, so for now it is enough to know it exists.

Trigger nodes vs poll nodes — why Gmail is always a beat behind

Underneath, event triggers split into two mechanisms, and that is what decides how fast they react:

The difference matters: Gmail Trigger does not run the moment mail arrives. Every X minutes n8n asks the Gmail API whether anything new has come in since it last asked. With a poll interval of 5 minutes, new mail waits up to 5 minutes before the workflow starts. To go faster, drop the poll interval to 1 minute (the shortest the Community edition allows), but you make more API calls and may run into the other side's rate limit.

Can one workflow have several triggers? Yes

n8n lets you put several Trigger nodes on one workflow. They sit side by side (not in series) — whichever one fires, the same downstream workflow runs. It is a useful pattern:

Pattern 1: Schedule + Manual (the most common)

The daily report goes out automatically at 8:00, but you suddenly want to send it again right now — add a Manual Trigger beside the Schedule Trigger, and pressing Execute Workflow runs it immediately. On the canvas it looks like this:

[Schedule Trigger]  ─┐
                       ├──▶ [Downstream node A] ─▶ [Downstream node B]
[Manual Trigger]    ─┘

Pattern 2: Webhook + Schedule (a safety net)

Normally the webhook reacts in real time, but in case a webhook is ever missed, add a Schedule that sweeps the database once an hour for anything left unprocessed and runs it again.

Pattern 3: several event triggers converging

"A message from Gmail or from Slack should open the same kind of ticket" — put a Gmail Trigger and a Slack Trigger side by side, share one set of downstream logic, and data from both sides takes the same path.

Hands-on: switch an existing workflow from Manual to Schedule

Say the workflow you built in Chapter 8 started with a Manual Trigger for testing (fair enough, Manual is the right choice while testing), and now that the testing is over you want it to run by itself at 9:30 every morning:

1. Open that workflow

   Go in through the Workflows list on the left. Right now it starts with a Manual Trigger node, with your existing downstream nodes to its right.

2. Delete the Manual Trigger node

   Right-click the Manual Trigger node → Delete (or select it and press Delete / Backspace). The connection to the downstream nodes breaks and the first downstream node is left "floating" on the canvas. Do not panic.

3. Add a Schedule Trigger

   Click + at the top left of the canvas (or press Tab on an empty spot) to open the nodes panel → pick On a schedule → Schedule Trigger. It drops onto the canvas.

4. Set the time on the Schedule Trigger

   Open the node panel: set Trigger Interval to Days, Days Between Triggers 1, Trigger at Hour 9, Trigger at Minute 30. Look at the Next execution shown under the node and check that the timezone in parentheses is Europe/London (or your intended IANA timezone) (if it is not, set it as described in the previous section).

5. Connect the Schedule Trigger to your existing downstream nodes

   Drag from the connector dot on the right of the Schedule Trigger to the dot on the left of the first downstream node. A successful connection shows as a solid line.

6. Save, then switch on the Active toggle at the top right

   Press Ctrl+S to save, then drag the Active toggle at the top right to green. This is the step everyone forgets — a Schedule with Active OFF never runs by itself, and crying about it tomorrow will not help.

7. Verify: press Execute Workflow once for a manual run

   Once it is Active you can still press Execute Workflow for a manual run, which tests whether the Schedule Trigger path makes it all the way through. If that run succeeds, tomorrow at 9:30 it will fire on its own.

8. Check the Executions page the next day

   In Executions on the left (or the Executions tab inside that workflow) you will see the record of the automatic run at 9:30 the next day. A record means the schedule is alive; no record means go to the next section and troubleshoot.

Common trigger pitfalls

The trigger did not fire, it fired at the wrong time, or it fired but nothing downstream ran — work through the five below and you can usually get yourself out of it.

FAQ