Skip to content

Triggers: what starts a workflow

Checked November 4, 2026

A trigger is the event that starts a run. The big split is how the tool finds out the event happened. Either it asks, or the app tells it. That's it.

What you need to know first

  • Which app holds the event, such as a form, a spreadsheet or a mailbox.
  • Whether that app can send a notification when something changes, or only answers when asked.
  • How fast you need the run to start.

Polling triggers

Think of checking a mailbox on a timer. Zapier describes polling as the tool asking your app for data every so often.1

The app sends back its latest items. Zapier then compares each item's unique ID to IDs it has seen before. A new ID starts a run. Nothing new? It waits and asks again.1

How a polling trigger finds new dataTimer firesTool asks the app for dataCompare with items already seenRun once per new item
The tool asks on a timer, then runs only for items it hasn't seen.

How long the tool waits between questions depends on the plan. Zapier's help page listed these on 4 November 2026.1

Zapier plan Polling interval
Free 15 minutes1
Professional 2 minutes1
Team 1 minute1
Enterprise 1 minute1

Plans and intervals change, so check the maker's page before you rely on a number. The same page says most triggers are polling triggers.1

Instant triggers

An instant trigger flips this around. The app pushes the news, and nobody has to ask. In Zapier's words, the app sends the new data by itself each time the event happens.1

The push usually travels as a webhook. Wikipedia explains that the site where the event happened sends an HTTP request to a web address you've set up for that purpose.2

Testing catches people out. Make notes that an instant trigger needs incoming info to run. Until data arrives, it just waits. So cause the event yourself, such as submitting the form, and then look at what the module received.3

Schedules

Some workflows don't wait for an event. They run on the clock. n8n's Schedule Trigger node runs workflows at fixed intervals and times.4 A weekly report fits that. A new-lead alert doesn't.

Things to know before you switch one on

  • You usually can't swap the type. Zapier says the trigger type is fixed and you cannot change it.1
  • Old data is skipped. A Zap won't trigger for old data, including data created before it was turned on.1
  • Loops can burn through your allowance. If a workflow writes back to the same app it watches, the update can retrigger it and create an infinite loop that rapidly consumes tasks.1
  • Waiting costs nothing in Zapier. Triggers never use tasks, and neither do the polls.5

Make counts differently. Its trigger modules only run once to check for or retrieve data, however many items come back.6 The counting rules of all three makers sit together in the last page of this set.

Once a trigger fires, the first step takes over. Actions and steps covers what happens next.

Cited material

  1. How Zap triggers work, Zapier Help Center
  2. Webhook, Wikipedia
  3. Mapping, Make Help Center
  4. Schedule Trigger, n8n Docs
  5. How is task usage measured in Zapier?, Zapier Help Center
  6. Operations, Make Help Center