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.

Best answer

1 Trigger use with 2 Separate Action case

  • January 6, 2021
  • 4 replies
  • 125 views
C

What if person using my app, use 1 trigger for 2 separate actions (meaning 2 zaps) instead of combining them like zapier recommends. I’m developing app, and i need to address this kind of situation.

Best answer by ikbelkirasan

@chinbatis - You have 2 options here:

  • Create a unique id in your database for each webhook subscription then return the id in the Subscribe function of the trigger. This will signal Zapier to save that ID, and it will be available via bundle.subscribeData.id in the Unsubscribe function. You can then send the id to your API to remove the webhook subscription.
  • Use the subscription URL itself as the webhook identifier in your database. bundle.targetUrl is also available in the Unsubscribe function.
    This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

    4 replies

    adamsmartschan
    Forum|alt.badge.img+6
    • adamsmartschanZapier Solution Partner
    • Zapier Solution Partner
    • January 6, 2021

    @chinbatis -

    Depending on the action in your app, the zaps would likely function fine. It’s not advisable – multi-step zaps keep things cleaner and more efficient – but I don’t think it would fundamentally break anything. 

    ikbelkirasan
    C
    ikbelkirasan
    Forum|alt.badge.img+12
    • ikbelkirasanZapier Solution Partner
    • Zapier Solution Partner
    • January 6, 2021

    @chinbatis - Let’s say both of the zaps use the same app and event as a trigger:

    • If the trigger is a webhook trigger then each zap will have a different subscription URL for the same event, so they will be triggered separately, which should work in your case.
    • If it’s a polling trigger then they will both poll the API for data, so if the zap 1 detects a new element A then zap 2 will detect it too because they run separately.

    Hope this helps!

    Ikbel – Zapier CLI App Specialist | Need custom triggers, actions, or searches? Want to automate what Zapier can’t do out of the box? Visit norapps.com or email info@norapps.net
    Troy Tessalone
    C
    C
    • chinbatisBeginner
    • Author
    • Beginner
    • January 7, 2021

    Thanks @ikbelkirasan . In this case i have to  store one or more subscription url for one trigger in my database. it should be fine if i could identify which subscription is canceled when user turns off the ZAP then i have to update the database to deactivate subscription.Which kind of data i could send along with the unsubscribed callback from zapier to my system? 

    ikbelkirasan
    Forum|alt.badge.img+12
    • ikbelkirasanZapier Solution Partner
    • Zapier Solution Partner
    • Answer
    • January 7, 2021

    @chinbatis - You have 2 options here:

    • Create a unique id in your database for each webhook subscription then return the id in the Subscribe function of the trigger. This will signal Zapier to save that ID, and it will be available via bundle.subscribeData.id in the Unsubscribe function. You can then send the id to your API to remove the webhook subscription.
    • Use the subscription URL itself as the webhook identifier in your database. bundle.targetUrl is also available in the Unsubscribe function.
    Ikbel – Zapier CLI App Specialist | Need custom triggers, actions, or searches? Want to automate what Zapier can’t do out of the box? Visit norapps.com or email info@norapps.net
    nicksimard
    C
    Terms & ConditionsAccessibility statement