Pipedrive won deals
Pipedrive Won Deal Testimonial Requests
Marking a deal won in Pipedrive is the moment the person behind it became a customer. StoryProof does not connect to Pipedrive, but from Pro an automation can be started by a call to its own webhook URL, and Zapier can make that call when a deal is won.
- Why a filter beats Pipedrive’s raw deal webhooks here
- Getting the person’s email, not just the deal
- A StoryProof wait that matches your delivery time
Checklist
From a won Pipedrive deal to a StoryProof email
Pipedrive items follow Pipedrive’s developer guide and Zapier’s Pipedrive page. Work top to bottom.
Your ticks are kept on this page only and never sent anywhere.
The problem, solved
Pipedrive wins that never turn into a story
- Problem 1
No StoryProof app in the Pipedrive marketplace
Without a listed app, the work falls back to salespeople emailing by hand.
How StoryProof solves it
From Pro, every automation has a secure URL. Zapier calls it when a deal matches your won filter.
- Problem 2
Won today, delivered next month
For services and projects, the customer has nothing to praise on the day the deal is marked won.
How StoryProof solves it
A wait of days or weeks, or until a chosen weekday and time, holds the request until the work has landed.
- Problem 3
One contact sits on several won deals
Repeat business means the same buyer appears in the filter again and again.
How StoryProof solves it
The review request step skips anyone who already reviewed or was asked recently.
- Problem 4
The first email gets buried
Busy clients often mean to answer and never do.
How StoryProof solves it
The follow-ups automation, from Pro, reminds them three days later and sends a last email four days after that, stopping once they respond.
- Problem 5
A win happened but no email went out
Was it the filter, the Zap or StoryProof? Guessing wastes an afternoon.
How StoryProof solves it
The automation log lists each webhook that arrived and the reason each run ended. It keeps 30 days.
Native Pipedrive webhooks versus a Zap
Pipedrive can send webhooks itself. For this job the limits below usually push teams to Zapier.
In StoryProof
The build in order
Step 1 of 4
Make the won filter in Pipedrive
Status equals won is enough for most pipelines. Add a pipeline condition if only one product line should ask.
Step 2 of 4
Build the StoryProof automation
Inbound webhook trigger, wait, review request. Keep it unpublished while you connect Zapier.
Step 3 of 4
Connect the Zap
Deal Matching Filter as trigger, an optional person lookup, then a JSON POST to the automation URL.
Step 4 of 4
Test on yourself, then publish
Mark a deal won with your own email as the person. Confirm the run in the log, then publish.
Before you start
Where this stops
No two way sync
StoryProof does not update the deal or the person in Pipedrive.
Your sample decides the fields
Pipedrive and Zapier field names vary by account. Check the fields the automation shows after you paste a sample.
Deals already won are skipped
The trigger reacts to new matches. Customers won before the Zap existed need a separate, manual ask.
Native webhook rules can bite
If you use Pipedrive webhooks anyway, Pipedrive caps each user at 40 and removes a webhook after 3 days of failures.
Docs, not a live test
The Pipedrive and Zapier steps follow their documentation as of 2026-11-18 and were not clicked through in a live account.
FAQ
Questions people ask
Short answers to what usually comes up next.
Why not use Updated Deal Stage instead of a filter?
Won is a deal status in Pipedrive rather than a pipeline stage, so a filter on status is the closer fit. If your team uses a final stage instead, Updated Deal Stage works too.
Can Make do this instead of Zapier?
Yes, if your Make account can watch Pipedrive deals. The call to StoryProof is an HTTP request module posting JSON to the automation URL.
What if a deal is reopened after it was won?
The run already started keeps going. Keep the wait realistic, and check the log if a deal changes hands.
Do salespeople still need to do anything?
Only keep the person and email on the deal accurate. The ask itself is sent by StoryProof.
Still have a question? Ask the StoryProof team or book a demo.
Let every won deal ask for a testimonial
Create the automation in StoryProof and give Zapier its URL.
Sources
- Guide for webhooks v2, Pipedrive Developers. Checked 2026-11-18.
- Webhooks, Pipedrive Knowledge Base. Checked 2026-11-18.
- Pipedrive integrations, Zapier. Checked 2026-11-18.
- Send webhooks in Zaps, Zapier Help Center. Checked 2026-11-18.
Last updated 2026-11-18.