A low-code solution to declaratively trigger webhooks based on changes and updates to your Postgres database. Useful for quickly setting up SMS notifications, transactional emails, automated payments, etc.

Hi Product Hunt! We made Quailrunner, and we're excited to soft launch and show it to you. Quailrunner is a low-code solution to trigger webhooks based on changes to your Postgres database. So far we've used it to set up SMS notifications, transactional emails, and automated payments in just a couple minutes for some side projects, and we think it can accomplish a lot more. We built Quailrunner based on the needs of previous companies and side projects to have a robust and dependable system to do things based on changes and updates to a database. We think it's better than a quick slapdash system for a couple reasons: - Idempotency and retries - Observability to see what's going right or wrong - Compatible with any third-party service with an API We're hoping Quailrunner can help you save some time building, or enable you to take care of some pesky features that would not otherwise be worth the effort. There's a free tier to give it a spin, but we also wanted to make sure the PH community got the full experience, so we've set up the promo code PHLAUNCH for a free month of the standard plan. We're really excited to get the community's feedback on this, specifically on - Bugs - UX and clarity of experience - Use cases (and if Quailrunner might work) We'll be active in the comments for quite a while, and you can also contact us at info@quailrunner.com. Thanks so much!

Hello @angelofu & team. A very interesting approach to attach automations directly to the DB, but the first thing that came to mind was security & privacy. I didn't see anything related to this on the landing page. And as far as I can tell the privacy page is just the generic type. It's a very attractive model, and seems easy to integrate, but now you have direct access to my DB? How are you handling this when it comes to privacy & data protection? I think this is a big deal to know. Does it all run locally? Do you receive only the requests that are triggered locally? If I was a potential customer, I would want more info here. Otherwise I really like the design, very unique and the UX is great. Easy to understand, and straight to the point. Just the privacy & "how it works" are missing from my point of view. Wish you all the best with this 🙌 Congrats :)

@angelofu Congratulations on the launch 🚀

Hey Angelo, Can it trigger multiple webhooks based on a single database update? Do you have plans to support databases beyond Postgres in the future? Congrats on the launch!

@kyrylosilin Hey, good question! Yep - setting up multiple triggers in Quailrunner would be the way to go for this. We're definitely planning to add support for more databases down the line, once we've got all the Postgres features nailed down. MySQL is probably next on the list.

This is such a useful product for triggering webhooks from Postgres but I think adding more detailed analytics or logs would take it to the next level. Being able to monitor exactly when and why a webhook fired or even seeing the performance impact could be valuable. Any plans to integrate logging features?

@grace_phillips1 Hi Grace! We already log the exact time a webhook was fired, and we provide some basic error logging if a webhook fails. The "why" of a webhook being fired is typically very simple in our mental model - it's that the SQL query you wrote returned a row and we haven't fired the webhook for that row yet. Thanks for taking a look! Would love to hear any other suggestions for observability you have.

Quailrunner

Low-code webhook initiation using your Postgres database

Do you use Quailrunner?