Different Types of Zapier Triggers

  • 29 January 2021
  • 3 replies
  • 1434 views
Different Types of Zapier Triggers
Userlevel 6
Badge +1

The trigger is a critical piece of our Zaps - as the trigger tells us when we have a new record to run the Zap for.

At the moment there are 3 main types of triggers that start Zaps.

Instant Triggers

With Instant triggers - something happens in the Trigger App and they immediately send a notification to Zapier.

This notification is what we use to trigger the Zap. (These are webhooks sent by the App to Zapier).

With an Instant trigger - your Zap will trigger immediately - regardless of your Zapier Plan.

 In Zapier we’ll see a Tag identifying the trigger as Instant.

Polling Triggers

With Polling triggers - instead of being notified by the App - we go out and look for changes (We ask the App for changes in your account via their API with a GET request).

We do this every X minutes based on your plan level. Free and Starter Plans are 15 minutes - all other Plans vary between 5 minutes to 1 minute.

With Polling Triggers we also check for records that already exist (or have already triggered the Zap) using a process called Deduplication.

In Zapier we can identify a Polling trigger by the lack of an Instant Tag.

 

Hybrid Triggers

Hybrid Triggers are essentially a mix of the Instant and Polling triggers.

With Hybrid triggers we are notified by the App that there has been a change - but they don't send much detail.

After we receive the notification we go and Poll for the details of the changes.

We also then run the Deduplication process on the data as well - similar to a Polling trigger.

These triggers may show as Instant in Zapier. But in reality the can take up to 3 minutes or so to trigger your Zaps.

Hybrid triggers are rare - and the 2 main Hybrid triggers in Zapier are the Google Sheets New Spreadsheet Row AND New or Updated Spreadsheet Row triggers - which you can see with the Instant tag in the screenshot below.

It’s worth noting here that the Google Sheets New Spreadsheet Row (Team Drive) AND New or Updated Spreadsheet Row (Team Drive) triggers are Polling triggers.

So these triggers are unique in that you can choose between using the Hybrid or Polling version of the trigger.

Can I Make a Polling Trigger Instant?

The quick answer is No.

We can't change the type of trigger - this is established when the Integration is programmed by the developers.

In some cases - you can configure the App to send a Webhook to Zapier - and use a Webhooks by Zapier Catch Hook Trigger.

But that solution would be dependent on the App you are using being able to send a webhook to Zapier.

Hopefully that provides some clarity on the different types of triggers that start Zaps. :)


3 replies

Userlevel 6
Badge +1

Hey @Thomas_LogxGroup!

First - I’d suggest you send in a support request so we can look at the specific Zaps and the log files for them.

https://zapier.com/app/get-help

The Quick Base New Record Trigger is a polling trigger.

We would check for new records based on the Polling Interval for your Plan. So for example Teams and Company Plans have 1 minute polling intervals - meaning each Zap would make 1440 requests each day (60 requests per hour * 24 hours) to Quick Base just for the polling requests.

If you had 100 of those Zaps - we’d be in the neighborhood of your 150k reads each day.

It can be slightly more complex than this - and the trigger can have additional reads it does such as pulling in the names of the columns/fields in the table.

In other words - the trigger might do 2 reads every time it polls for new records - one to get the table data and one to get the records.

Userlevel 1

Thank you Jared, for the quick reply.  

Your information has been very helpful and points us in the right direction.  I’ll talk with the team and review what has been done and follow up accordingly. 

Regards,

Thomas

Userlevel 1

Jared,

Question: Quickbase new record event an instant or polling trigger?  Reason I ask is because we are seeing 1500 new records today but noticed that there’s 150000 reads to the table in Quickbase from Zaps.

Now the curveball; we have many zaps that trigger based off of the new record event from Quick base (same table) but criteria is different for each one.  Is it correct to assume the larger than expected reads are driven off of each event having to determine if the specific criteria has been met?

Reply