Skip to main content
Best answer

Migration to new endpoint


Hello,

 

Can someone tell me how Zapier knows if some entry is already processed? I have a situation where I am changing application from where Zapier gets data to process and I am curious on which field (maybe id?) Zapier knows that some entries are already processed when it pulls the data.

 

Thanks in advance

Best answer by ZaneBest answer by Zane

For polling triggers the id field in each object from your API governs deduplication. Zapier won’t process the the same ID twice while the Zap is enabled. That last part’s important to know about. The “deplication database” is rebuilt each time a Zap is enabled. In other words if a Zap is paused, and 12 new items were added, those 12 items would not be handled. They’d be added to the dedup database and only new items found after that inital poll request would be processed by the Zap. 

If you’re changing an endpoint, make sure the change is non-breaking to ensure your users’ continuity: Same auth, same trigger and action key names, say existing set of input field key names and types, no new required fields, and the same output, etc. With non-breaking changes you’ll be able to migrate users’s Zaps to the new version of your integration without interruption. 

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

  • Author
  • Beginner
  • 4 replies
  • March 25, 2022

In meanwhile I found out that same id as a field would be sufficient to prevent duplicate 


Forum|alt.badge.img+9
  • Zapier Staff
  • 331 replies
  • Answer
  • March 25, 2022

For polling triggers the id field in each object from your API governs deduplication. Zapier won’t process the the same ID twice while the Zap is enabled. That last part’s important to know about. The “deplication database” is rebuilt each time a Zap is enabled. In other words if a Zap is paused, and 12 new items were added, those 12 items would not be handled. They’d be added to the dedup database and only new items found after that inital poll request would be processed by the Zap. 

If you’re changing an endpoint, make sure the change is non-breaking to ensure your users’ continuity: Same auth, same trigger and action key names, say existing set of input field key names and types, no new required fields, and the same output, etc. With non-breaking changes you’ll be able to migrate users’s Zaps to the new version of your integration without interruption. 


  • Author
  • Beginner
  • 4 replies
  • March 28, 2022

thanks for detailed response