Trigger Node
The starting node of a workflow automation that fires when an external event happens: webhook received, schedule met, database row changed, email arrived.
Last updated: April 26, 2026
Definition
A trigger node is what kicks off a workflow in n8n, Make, Zapier, and similar platforms. It defines the entry condition: on every new row in a table, on every webhook POST, every 5 minutes via cron, on every Slack message containing a keyword. The rest of the workflow (including any agent loops) runs only when the trigger fires. Triggers are how AI agents become reactive: instead of running continuously, the agent runs in response to a real-world event. n8n offers 100+ built-in triggers; the most common in agent workflows are webhook, schedule, and database change triggers.
When To Use
Use a trigger node whenever an agent needs to respond to external events rather than poll. Webhooks are the simplest and most common; schedules cover periodic batch work; database triggers handle CRM and ops integration.
Sources
Related Terms
Building with Trigger Node?
I've shipped this pattern in real production systems. If you want a second pair of eyes on your architecture, that's what I do.