Solving Webhook Triggering Loop in Make.com

Have you ever found yourself in a situation where you're setting up a scenario in Make.com where a deal update in Pipedrive triggers a webhook, but then it starts triggering in a loop every few seconds? It can be quite frustrating, right? But don't worry, we've got a solution for you.

The Problem

When you set up a scenario in Make.com where Pipedrive is the trigger (i.e., a deal is updated) and one of the actions is a Webhook, you might encounter a problem. If that Webhook causes another update on the deal, it triggers the Scenario again, causing a loop.

The Solution

The solution to this problem is to add a filter. This filter should be placed between the trigger module and whatever module comes after it. The purpose of this filter is to ensure that it only allows updated deals that aren’t caused by the Webhook.

For instance, if you have a module adding an activity and in the deal, there is a field called “undone_activities_count” which changes after an activity is created, you can add a filter to solve the problem.

Troubleshooting Tips

If you're still experiencing the loop, double-check your filter settings. Make sure that the filter is correctly set to only allow updates that aren't caused by the Webhook. Also, check if the field that changes after an activity is created is correctly identified in the filter.

Conclusion

In conclusion, the key to solving the problem of a Webhook triggering in a loop in a Make.com scenario is to add a filter that only allows updates not caused by the Webhook. It might take a bit of tweaking and adjusting, but once you get it right, you'll have a smoothly running scenario.

You do have further questions?

Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.