Skip to main content

Hello everybody

First - Happy holidays!

Second - kind of a general question

If I use a set of conditions to trigger a zap - for example :

Trigger - Project was updated (where every status or stage changes as well as field updates is considered a project update)

Filter on a particular stage and status of the project.

 

The question is after the first time when these conditions are met and the zap run successfully, assuming the filter conditions are static, will every subsequent update to the project trigger the zap again?

 

I hope this is clear 

Thanks

Hi @crelis 

Depends on the Zap trigger behavior, but yes it can happen.

You may need to keep a log in a GSheet or Airtable Base to check against and then Filter again.

Zapier has some built in deduplication: https://zapier.com/help/create/basics/data-deduplication-in-zaps


Thanks!

I saw in the documentation trigger filters and also custom filters 

I am not sure I get what  the difference is 


@crelis 

Trigger filters are included in the Zapier trigger step to limit what events cause the Zap to fire.

Filters are actions steps that can be configured in a Zap: https://zapier.com/apps/filter/help


Thanks…..I use the filters all the time

What I wasn't sure was the difference between trigger filters and custom filters. Is this to do with the stage of the Zap where the filter is placed? If the filter is placed just after the trigger it is a trigger filter and if its anywhere else in the zap (like path) it is considered a custom filter?


@crelis

Trigger filters existing in Step 1.

Action Filters exists as Steps 2+: https://zapier.com/apps/filter/help

TIP: When in doubt, test it out!


@Troy Tessalone - No need to reply to this one….

If the documentation used the term “Action” Filters it would be clear. However, the term used is Custom filters which I guess to a novice user like myself was slightly confusing.