n8n Trigger Nodes: Complete Guide to Starting Your Workflows

Every n8n workflow starts with a trigger node. The trigger is what wakes up your workflow and tells it to run — whether that’s a scheduled time, an incoming webhook, a new email, a form submission, or a manual button click. Understanding trigger nodes is one of the most important fundamentals in n8n because the trigger you choose shapes everything else about how your automation behaves.

In this guide, we break down every major trigger type available in n8n, explain when to use each one, and show you practical examples of how they fit into real automation workflows.

What Is a Trigger Node?

A trigger node is always the first node in an n8n workflow. It defines the event or condition that causes the workflow to execute. Without a trigger, a workflow can only be run manually from inside the n8n editor — it can’t run automatically on its own.

Trigger nodes are visually distinguished in the n8n editor by a lightning bolt icon. When you create a new workflow, n8n prompts you to choose a trigger first. You can always change or add to this later, and some advanced workflows use multiple triggers — though each trigger creates its own independent execution path from the start of the workflow.

Manual Trigger

The Manual Trigger is the simplest trigger in n8n. It does exactly what it sounds like — it runs the workflow only when you click the “Execute Workflow” button inside the n8n editor. There is no automation involved. The Manual Trigger is most useful while you’re building and testing a workflow. You can kick it off on demand to see how the rest of your nodes behave with real data.

Once your workflow is production-ready, you’ll typically swap the Manual Trigger for something that runs automatically — a schedule, a webhook, or an app-specific trigger. But during development, the Manual Trigger is your best friend for fast iteration.

Schedule Trigger

The Schedule Trigger runs your workflow at defined intervals or at specific times. It supports multiple scheduling modes: every N minutes or hours, daily at a specific time, weekly on certain days, monthly on a certain date, or via a fully custom Cron expression for precise timing control.

To use it, add the Schedule Trigger node and set your desired interval. Common use cases include running a daily report at 8am, syncing data between two systems every hour, sending a weekly summary email every Monday morning, or archiving records at midnight on the first of each month. The Schedule Trigger is one of the most widely used triggers in production n8n deployments.

Webhook Trigger

The Webhook Trigger gives your workflow a unique URL that external services can POST or GET data to. When that URL receives a request, the workflow fires immediately with the incoming data available as the trigger output. This makes it the go-to trigger for real-time integrations where external systems need to push events to n8n.

Common uses include receiving Stripe payment confirmations, processing form submissions from a website, handling GitHub push events, or accepting data from a custom-built app. The Webhook node supports GET, POST, PUT, PATCH, and DELETE methods, and you can configure authentication (header auth, basic auth, or no auth) to secure the endpoint. You can also configure whether the webhook responds immediately or waits for the workflow to finish before returning a response.

App-Specific Triggers

Many n8n integrations include their own dedicated trigger nodes that poll or subscribe to events within a specific app. For example, the Gmail Trigger checks for new emails matching a filter, the Airtable Trigger fires when records are created or updated, and the Slack Trigger activates on new messages or reactions. These app-specific triggers handle the complexity of authenticating with the service and checking for new events so you don’t have to build that logic yourself.

App triggers typically operate in one of two modes: polling (n8n checks the service on a regular interval, typically every minute) or webhook/real-time (the service pushes events to n8n instantly). Real-time triggers are faster but require the app to support webhooks. Polling triggers work with virtually any app but introduce a slight delay between the event occurring and the workflow running.

Chat Trigger

The Chat Trigger is designed for AI-powered conversational workflows. It provides a built-in chat interface that you can embed in a webpage or use directly in n8n’s test environment. When someone types a message, the Chat Trigger fires the workflow with the message content as input. This is the standard starting point for building n8n AI agents, chatbots, and conversational automation.

The Chat Trigger integrates naturally with the AI Agent node — you connect the trigger to the agent, and the agent uses the incoming message to decide what tools to call and what to respond with. It supports session memory, meaning the agent can maintain context across multiple messages in a conversation.

Form Trigger

The Form Trigger generates a hosted form with fields you define — text inputs, dropdowns, date pickers, file uploads, and more. When someone submits the form, the workflow fires with all the submitted field values available as trigger output. No external form builder required.

This is ideal for collecting structured data and routing it into a workflow immediately. Use cases include intake forms for client onboarding, internal request forms for IT or HR processes, event registration, lead capture, or any scenario where you want a simple form that directly triggers automation without involving a third-party tool.

Choosing the Right Trigger

The right trigger depends entirely on what should initiate your workflow. Ask yourself: should this run on a schedule, or in response to an event? If it’s time-based, use the Schedule Trigger. If it’s event-based, determine whether the event comes from an external system pushing data (Webhook Trigger), an app you’re integrated with (app-specific trigger), a person typing (Chat or Form Trigger), or you clicking a button (Manual Trigger).

A helpful pattern when starting out: build and test with the Manual Trigger, then switch to the real trigger once the workflow logic is solid. This lets you iterate quickly without worrying about timing or incoming data formats until you’re ready.