Skip to main content
Question

Webhook keeps firing—what response should i send to avoid duplicate entries?

  • October 11, 2024
  • 2 replies
  • 56 views

Hi there,

 

So have a Zap that receives every transaction and then sends that transaction to a Webhook in Make.com that then puts it into my Notion database. The problem is that it fires the Webhook multiple times, probably (as what I'ge read on the internet) because the Zapier Webhook needs to get a verification that the Webhook was received. I tried a Webhook response with "200" but that didn't work. Does anyone know what I should do?

 

Thanks!

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.

2 replies

Troy Tessalone
Forum|alt.badge.img+14
  • Zapier Expert
  • 30739 replies
  • October 11, 2024

Hi @Liam Joy Niemeijer 

Help links for using webhooks in each platform:

https://zapier.com/apps/webhook/help

https://www.make.com/en/help/tools/webhooks

 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode.

Post screenshots showing examples of the multiple firing of the webhook.


Troy Tessalone wrote:

Hi @Liam Joy Niemeijer 

Help links for using webhooks in each platform:

https://snapchatplanetorder.com/

https://www.make.com/en/help/tools/webhooks

 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode.

Post screenshots showing examples of the multiple firing of the webhook.

To prevent duplicate entries when a webhook keeps firing, it's essential to implement idempotency in your response. When the webhook is triggered, your system should check if the event has already been processed by verifying a unique event ID or timestamp included in the webhook payload. If the event has already been recorded, respond with a status code like 200 OK or 204 No Content to acknowledge receipt without re-processing it.