---
title: "Comment by Chris Webb on \"Unleash Powerful Webhooks with pgwebhook in Supabase\" | Hashnode"
description: "Is there a concern with using pg_http with triggers because it is synchronous whereas pg_net is asynchronous?"
url: "https://hashnode.com/posts/unleash-powerful-webhooks-with-pgwebhook/667b0cad03043fa108e78a29/comment/66b4a3e43cbc791a8997adcc"
---

[Discussion](https://hashnode.com/posts/unleash-powerful-webhooks-with-pgwebhook/667b0cad03043fa108e78a29)

Comment [Unleash Powerful Webhooks with pgwebhook in Supabase](https://hashnode.com/posts/unleash-powerful-webhooks-with-pgwebhook/667b0cad03043fa108e78a29)

[Chris Webb](https://hashnode.com/@tazmaniax)

[Aug 8, 2024](https://hashnode.com/posts/unleash-powerful-webhooks-with-pgwebhook/667b0cad03043fa108e78a29/comment/66b4a3e43cbc791a8997adcc)

Is there a concern with using pg\_http with triggers because it is synchronous whereas pg\_net is asynchronous?

[Rodrigo Mansueli](https://hashnode.com/@mansueli)

[Aug 8, 2024](https://hashnode.com/posts/unleash-powerful-webhooks-with-pgwebhook/667b0cad03043fa108e78a29/comment/66b4a3e43cbc791a8997adcc#reply-66b4b1f885676b9484f758c6)

Yes, this concern is valid, and it comes down to whether the webhook is essential to your logic.

This is a better solution if you need to ensure a response from the hook. If you are fine with failures on the webhook, then you can use the default hooks with async behavior is superior.

A third option is to have a queue with retries using async logic. You can use supa\_queue for that:

[github.com/mansueli/supa\_queue](https://github.com/mansueli/supa_queue)
