Bug Fix

Fix Zapier 'New Person' Zaps that stopped firing after toggling the Zap

What We Fixed

When a customer toggled a Sure Send Zap off and back on in Zapier — or edited and re-saved it — Sure Send stored a new webhook subscription each time, without deactivating the previous ones. Every new lead then fanned out to all the historical Zapier URLs, but only the most recent URL was the live subscription. The older URLs accepted the delivery and silently discarded it, so the Zap appeared healthy on our side while the customer’s downstream CRM never received the lead until they manually pulled records in Zapier.

The Zapier subscribe handler now consolidates onto a single active subscription per event: it updates the existing row’s URL to the latest one Zapier issued and disables any older duplicates. Customers affected by this will be self-healed on their next Zap save/toggle — no action required on their part beyond triggering one more re-subscribe.