Yes, this is possible with either Zapier or Make. I would highly recommend using Make’s PipeDrive integrations along with Make’s Airtable integrations.
That’s because Make is infinitely more powerful & customizable than Zapier, yet it is significantly cheaper than Zapier. I wrote an entire post here comparing Make vs. Zapier.
If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.
I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.
Hope this helps!
If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld
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
Hi Mark, I understand your challenge with trying to trigger a specific action in Airtable only when a deal is "won" in Pipedrive, and how the standard Zapier triggers might seem too broad.
ScottWorld's suggestion of using a conditional path in Zapier is a solid, no-code approach to filter out unwanted updates, or switching to an alternative like Make (formerly Integromat), which often gives you more control over those conditional workflows at a potentially lower cost.
Beyond the no-code tools, for a highly reliable and immediate solution, you could explore a custom server-side approach leveraging the Pipedrive API, the Airtable API, and a server environment.
Pipedrive's API is robust and supports webhooks for instant notifications on specific events, including when a deal status changes to won, which is exactly what you need.
This eliminates the need for polling and checking "all updates."
You would configure a Pipedrive webhook to send an instant JSON payload to a specific URL when the deal object is updated and the status changes to won.
The server environment could be something like Google Cloud Platform (GCP) or a specialized server-side container platform like Stape.
When Pipedrive's webhook sends the data, it hits an endpoint you've set up, potentially within a Google Tag Manager (GTM) server container that is hosted on Stape or GCP.
Using a GTM server container, even though traditionally for marketing tags, allows you to receive and process HTTP requests from a webhook, which is then managed through a custom tag or client.
Although a direct, native integration between Airtable and GTM for simply sending data isn't possible because Airtable can't host the GTM container, this server-side setup acts as the perfect middleman.
The custom GTM tag, or a script running on GCP, would take the "won" deal data from the Pipedrive webhook and execute a direct API call to the Airtable API to create the new record.
This approach offers maximum flexibility, immediate execution upon the deal being "won", and a single, custom point of control for the entire data transfer, making it a very powerful and precise automation.
