Skip to main content

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.

In Pipedrive
In StoryProof
In Zapier
First run

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.

  • 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.

  • Problem 3

    One contact sits on several won deals

    Repeat business means the same buyer appears in the filter again and again.

  • Problem 4

    The first email gets buried

    Busy clients often mean to answer and never do.

  • Problem 5

    A win happened but no email went out

    Was it the filter, the Zap or StoryProof? Guessing wastes an afternoon.

Native Pipedrive webhooks versus a Zap

Pipedrive can send webhooks itself. For this job the limits below usually push teams to Zapier.

Pipedrive details from its webhooks v2 developer guide; Zapier trigger from its Pipedrive page. Both read 2026-11-18.
PointPipedrive webhook (change, deal)Zapier Deal Matching Filter
What fires itAny change to any dealA deal matching your filter for the first time
Filtering to wonNot available on the subscription; you would filter after deliveryBuilt into the Pipedrive filter you choose
Failure handlingThree retries; deleted after 3 days with no successful deliveryVisible in Zap history
AuthenticationOptional HTTP basic auth user and passwordHeaders and Data fields you control

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.

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

  1. Guide for webhooks v2, Pipedrive Developers. Checked 2026-11-18.
  2. Webhooks, Pipedrive Knowledge Base. Checked 2026-11-18.
  3. Pipedrive integrations, Zapier. Checked 2026-11-18.
  4. Send webhooks in Zaps, Zapier Help Center. Checked 2026-11-18.

Last updated 2026-11-18.