Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Subject: Pipeline CRM "Deal Status Changed" Webhook Not Firing - Tests Work But Real Changes Don't Trigger

What I'm trying to accomplish: Set up a Zap that triggers when deals in Pipeline CRM move to "Won" status and automatically adds a row to my "Jondec Schedule" Smartsheet with the deal details.

Current Zap Configuration:

  • Trigger: Pipeline CRM - Deal Status Changed → "Won" status (ID: 373903)
  • Action: Smartsheet - Add Row to "Jondec Schedule" sheet
  • Field Mappings: Deal name, value, estimator, dates, contact info, deal ID

What's Working: ✅ Manual tests of both steps work perfectly
✅ Authentication is configured correctly
✅ Smartsheet gets populated correctly during tests
✅ All field mappings are proper

What's NOT Working: ❌ Real deal status changes in Pipeline CRM don't trigger the Zap
❌ No entries appear in Task History when I change actual deals
❌ Webhook connection seems broken despite published Zap

Troubleshooting Already Attempted:

  • Verified I'm moving deals to correct "Won" status (not "Won-BD")
  • Confirmed deals were NOT already in "Won" status before changing
  • Published/republished the Zap multiple times
  • Waited 10+ minutes for webhook connection to establish
  • Tested with different deals and different status changes
  • Verified Pipeline CRM account matches connected account in Zapier

Technical Details:

  • Pipeline CRM account: XXXX@XXXXXX.com
  • Multiple "Won" statuses exist: "Won" (373903) and "Won-BD" (2520725)
  • Using the correct "Won" status in trigger
  • Zap shows as published but editor sometimes shows draft mode

Question: Is this a known issue with Pipeline CRM webhooks? The manual tests prove the integration works, but real-time triggers never fire. Any suggestions for getting the webhook connection to work properly?

This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.

Hi ​@JerryG 

 

We submitted a bug report for this earlier, and here’s the response we got from the Pipeline CRM developers.
 

The "Deal Status Changed" triggers only when deal status changes and "Deal Status" should be the only available field for this trigger.

To build Zaps that trigger on deal stage change, customers should use "Moved Deal" trigger instead. This trigger has a simmilar error - in addition "Deal Stage" it lists 2 other fields that are irrelevant for this trigger.

 

If your Zap’s trigger is currently set to monitor a different field than “Status”, then it won’t trigger. For instance, if it is set to trigger when the “Stage” changes, then you should use “Moved Deal” trigger instead.

I hope that helps.

Terms & ConditionsAccessibility statement