Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Zapier takes too long to start after something happens

Short answer

Many Zapier triggers poll: Zapier asks the app for new data at an interval, which is 15 minutes on the Free plan and 1 to 2 minutes on paid plans. Instant triggers use webhooks and are usually faster, but an app's API decides which one a trigger is.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A new order shows up in my other app ten or more minutes later.
  • Customers wait for a confirmation that should be instant.
  • Testing works but live is slow.
  • The trigger stopped firing with no error.
  • Some Zaps are fast and others slow.

Why does this happen?

  1. Polling triggers check on a schedule

    Zapier's published intervals are 15 minutes on Free, 2 minutes on Professional and 1 minute on Team and Enterprise. Between checks, new data waits.

  2. Instant triggers are webhooks

    Instant triggers, marked with a lightning bolt in the editor, receive data as soon as the app sends it. The trigger type is set by the app's API, so you cannot switch one to the other.

  3. A stalled connection stops firing silently

    Zapier suggests that if a trigger stops without errors, you turn the Zap off, wait about a minute and turn it on to reset the connection.

  4. Heavy traffic can delay later steps

    For webhook triggers, rate limits apply and heavy simultaneous traffic can delay data reaching later steps.

What can I do about it today?

  1. Find the trigger typeOpen the Zap editor and look for the lightning bolt on the trigger.
  2. Check your plan's intervalIf a polling trigger is slow and the interval matches your plan, it is working as designed.
  3. Decide how fast you need itA report once an hour does not need seconds. A payment confirmation might.
  4. Try the resetIf nothing fires, turn the Zap off, wait about a minute, and turn it back on.
  5. Poll manually for urgent checksThe editor can check for new data on demand, which is useful when testing.

When should I bring someone in?

  • Customers or staff are waiting on the automation.
  • The app has no instant trigger and speed matters to the business.
  • Events arrive in bursts and some seem lost.

How do I handle it?

  1. Measure the real delayI compare event time and Zap start time over a day, not one example.
  2. Check what the source app offersWebhooks or a direct API call may give an instant start where a polling trigger cannot.
  3. Move only what must be fastTime-critical steps get a webhook-based path, with retries and logging. Everything else can stay on a schedule.
  4. Test with burstsI send several events at once to check order and loss, before switching over.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I make a polling trigger instant?

Zapier says you cannot switch a trigger between polling and instant, because the app's API sets the type. You can shorten the interval on Professional, Team and Enterprise plans.

Why is a test fast but live slow?

Tests can fetch data immediately. Live runs wait for the next polling interval.

Is a 15 minute delay a fault?

On the Free plan it is the published interval, so it is by design.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.