Trigger nodes: how workflows start

n8n · Essentials · 8 min

The trigger decides when your workflow runs and what data it starts with.

Every workflow that runs on its own starts with a trigger node. Common ones:

  • Manual Trigger ("When clicking Execute workflow"): only runs when you click. Good for building and one-off jobs.
  • Schedule Trigger: runs on a timetable, such as every day at 8:00 or every 15 minutes. Check the time zone in the workflow settings.
  • App triggers: many app nodes have a trigger version, such as "Gmail Trigger: on message received" or "Google Sheets Trigger: row added". Some are notified instantly by the app; others check for changes on a timer (called polling).
  • n8n Form Trigger: n8n hosts a simple web form for you, and each submission starts the workflow.
  • Chat Trigger: a chat window for talking to an AI agent (covered in the AI module).
  • Webhook: a web address that any other system can call to start the workflow (its own lesson later).
  • Error Trigger and Execute Workflow Trigger: special triggers for error handling and sub-workflows, covered later.

A workflow can have more than one trigger, for example a schedule plus a manual trigger for testing.

In n8n 2.x the old "Start" node no longer exists; use the Manual Trigger instead.

Important: most triggers only fire on their own after the workflow is published (made live, covered in a later lesson). While building, you start them by hand or use a "listen for test event" button.

Remember

  • Manual, Schedule, app, Form, Chat and Webhook triggers cover most needs
  • App triggers are either instant or polling
  • Triggers fire automatically only after the workflow is published

Check yourself

  1. You want a report built every Monday at 9:00. Which trigger fits?

Sign in to answer, see the explanations, and get this lesson back as a quick review later.

Official docs: docs.n8n.io/build/understand-workflows/create-and-run-workflows