In general, the way that this typically works (in a no-code/low-code way) is that you would monitor for ALL updates, and then only continue your zap if the order is “won”.

In Zapier, you do that by creating a conditional path. So your conditional path would only continue if the update that was just sent to Zapier was a “won” order.

However, for me personally, I find it much easier to use Integromat to do this, because it’s significantly easier to visualize & control conditional paths in Integromat (and Integromat is much cheaper than Zapier, too).

In Integromat, you use “filters” and “routers” for your conditional paths:

Note that if you want to get even more advanced, you can dive into custom API calls, custom data storage, and/or custom JavaScripting. In those cases, you can typically do searches ONLY for your “won” orders, but that gets more tricky because you also need to keep track of the last time you did a search so you don’t keep returning the same results over & over again. It’s just a little bit more of a complex puzzle that you need to figure out.

p.s. I’m an Integromat Partner and an Airtable consultant — if you ever need to hire an expert to help, feel free to contact me through my website at scottworld.com.

Hi Mark!

It's been a few years, so not sure if this is still an issue you're trying to solve, but wanted to share that Whalesync just launched a 2-way sync Pipedrive integration that works with Airtable and would fix this.

https://www.whalesync.com/sync/pipedrive-airtable