Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 36 ยท Automation Concepts

Polling vs Instant Triggers: How Zaps Start

Learn how polling triggers check for new data on a schedule, how instant triggers use webhooks, why dedup and batches matter, and simulate both with runnable Python.

How does a Zap know that something happened? There are two basic mechanisms, and the difference explains delays, duplicates and missed events. Understanding polling and instant (push) triggers lets you choose the right trigger and explain to a colleague why "it took 15 minutes".

Zapier cannot run on this site. The Python blocks are stand-ins that model both mechanisms. Exact polling intervals depend on your plan and may change; check Zapier's current documentation.

Polling triggers

With polling, Zapier asks the app on a schedule: "What is new since last time?" The interval depends on the plan: faster on higher plans, slower on free ones. Each check returns recent items (often a limited number of the newest), and Zapier compares them with items it has already seen, using an ID or a sort field.

sequenceDiagram
  participant Z as Automation platform
  participant A as App
  loop every interval
    Z->>A: Any new items?
    A-->>Z: List of recent items
    Z->>Z: Skip seen ids, run Zap for new ones
  end

Polling is simple and works with any app that has an API, but there is always a delay of up to one interval.

Pros: works for almost any app; predictable. Cons: delay; if more new items arrive than one check can return, the oldest may be missed; apps with weak sorting cause duplicates or missing records.

Instant triggers

With an instant trigger the app tells Zapier immediately, through a webhook (an HTTP call from the app to a URL Zapier gives it). When an event happens, the app sends a small message and the Zap starts within seconds. In the editor, instant triggers are often marked as such. The app must support webhooks, and sometimes you must configure the webhook inside the app.

Pros: fast; no wasted checks. Cons: if Zapier is unreachable at that moment, the event may be lost unless the app retries; some apps need setup.

Webhooks also let you send data to Zapier from your own code, covered in chapter 5.

Time-based triggers

A schedule trigger runs at times you pick: every hour, every weekday at 9:00, the first day of the month. Choose the time zone explicitly. These are ideal for reports and cleanups.

Simulating polling

This stand-in models an app with a stream of items and a poller that only sees the newest few items per check. Watch what happens when items arrive faster than the poller keeps up.

Python Stand-in: polling can miss items

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

With two arrivals per interval, nothing is lost. With five, the poller never sees some items. Real platforms mitigate this in various ways, but the lesson stands: for high-volume sources prefer instant triggers or smaller intervals.

Simulating instant delivery and retry

An instant trigger depends on delivery. This stand-in models a webhook sender that retries when the receiver is down, plus the receiver's de-duplication.

Python Stand-in: webhook delivery with retries and dedup

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

This is why good senders retry and good receivers are idempotent, tying back to the mental model.

Choosing between them

Situation Prefer
Customer-facing, needs a fast reaction Instant
App has no webhooks Polling
Low volume, delay is fine Polling is fine
Very high volume Instant, or batch processing
Reports and reminders Schedule

Practical tips

  • Read the trigger's description: it often says "instant" or states the typical delay.
  • When a polling trigger seems to miss data, check how the source sorts items (newest first is best).
  • Avoid triggers whose source changes the same record many times; you may run more than you expect.
  • If an event must never be lost, add a reconciliation Zap that runs on a schedule and looks for records not processed yet.
  • Keep the trigger as specific as possible ("new row in this sheet") rather than broad ("any change").

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main downside of a polling trigger?

    Polling only checks periodically, so events wait until the next check.
  2. 2. How does an instant trigger learn about an event?

    The source app pushes a message to a URL, starting the Zap within seconds.
  3. 3. A receiver gets the same event ID twice. What is the right behavior?

    De-duplicating by event ID keeps repeated deliveries harmless.
  4. 4. Which source is best served by a schedule trigger?

    Reports and reminders depend on time, not on an app event.

Summary

  • Polling checks on a schedule and can lag or miss items under load.
  • Instant triggers use webhooks and react in seconds but rely on delivery and retries.
  • Schedule triggers suit reports and reminders; set the time zone.
  • Receivers should de-duplicate by ID; senders should retry.
  • Add reconciliation for events that must never be lost.

Next: What to Automate: Process Mapping and ROI