Skip to main content
Question

Managing subscriptions when testing triggers in Zapier

  • November 25, 2025
  • 1 reply
  • 39 views

When i test a trigger it creates a subscription. I can see in this post “That subscription should be garbage-collected within a few hours using the `performUnsubscribe`.” But i can’t see any other mention of this in the documentation. It also doesn’t seem to be happening while i have been testing today. In the bundle meta there’s also an isLoadingSample field that, if this run was initiated manually via the Zap Editor should be true but this is always coming through as false. How should i manage these? Am i missing something? 

1 reply

ikbelkirasan
Forum|alt.badge.img+12
  • Zapier Solution Partner
  • November 28, 2025

Hi ​@asdasdadsda 

Calling performSubscribe and letting Zapier auto–garbage-collect it later is definitely an undocumented behavior as far as I know. But that only happens if you don’t define performList. When you test a webhook trigger, Zapier calls performList, and if it’s missing, it falls back to creating a real subscription.

 

As for your other question, isLoadingSample is used in polling triggers because they only have a single `perform` function. The flag helps you know whether the step is being tested in the editor or running live (assuming no other flags like isPopulatingDedupe are set).

 

Webhook triggers work differently since Zapier will call performList during testing, so it makes sense that isLoadingSample isn’t used there.