Hello HN,<p>We’d like to show you our project — Nohooks[0]. The aim is to add webhooks to platforms that do not natively support webhooks. We really believe many APIs can provide a better developer experience by providing webhook notifications to enable us to automate more things.<p>Nohooks works by intelligently polling the integrated platform's APIs, determining if a change has occurred, and generating webhook events. Nohooks currently supports webhooks from Notion’s Databases, Render’s Services & Deployments, and DigitalOcean’s Droplets. We will add more in the coming days and improve the types of events/payloads generated to enable new workflows that were previously impossible or difficult to achieve. It uses Convoy[1] to power its webhooks delivery and debugging dashboard.<p>We welcome you to try it out and give us your feedback — what platform would you love to have webhooks for that doesn’t currently exist? What webhooks best practices would you like to see implemented?<p>[0]<a href="https://nohooks.io" rel="nofollow noreferrer">https://nohooks.io</a><p>[1]<a href="https://github.com/frain-dev/convoy">https://github.com/frain-dev/convoy</a>
Pipedream has a similar paradigm, and Notion support as well.<p><a href="https://pipedream.com/apps/notion" rel="nofollow noreferrer">https://pipedream.com/apps/notion</a><p>You can write your own "Sources" that can poll any API, it even includes deduping for free: <a href="https://pipedream.com/docs/components" rel="nofollow noreferrer">https://pipedream.com/docs/components</a>.<p>I build custom sources all of the time for scraping RSS feeds, WooCommerce stores, and then triggering low code workflows as if they are webhooks.
Cool idea. What happens when these services do start offering webhooks?<p>What does “intelligently” polling mean?<p>You’d basically have to poll on some schedule (ideally configured by the user).
Update: Nohooks Backend is now open source [0]. The goal is to collectively improve the polling system as well as generate more useful event types/payloads.<p>It was written in Rails :D<p>[0] <a href="https://github.com/frain-dev/nohooks-backend">https://github.com/frain-dev/nohooks-backend</a>
That's super cool and this looks more like a POC than a product for now, but if this were to take off, it would complement really well what we do in our own OSS project windmill.dev [1] where users can deploy scripts in typescript/python/go/bash and more complex flows composed out of those same scripts, get a webhook and a UI to trigger them. Users currently have to either set a schedule to regularly poll or setup a webhook on the event source. This would be a consolidated way for them to have all their event sources in the same place.<p>[1]: <a href="https://github.com/windmill-labs/windmill">https://github.com/windmill-labs/windmill</a>
Ever heard of HTTP error 429?<p>We got it from providers where our clients sent too many requests<p><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429" rel="nofollow noreferrer">https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429</a>
It's unbelievable that Notion DB does not have webhooks.<p>And still, your business model depends on these platforms not having features, so your market can be easily captured by them as soon as you grow big enough to be noticed.
I still didn't find an explanation of what's the difference between callbacks with self service user maintainable HTTP url targets and what is now called webhooks. Can anyone here please elucidate?
I own NotionWebhook.com and I have not deployed my service yet which offers exactly the same. you can DM me here <a href="https://twitter.com/rajasimon" rel="nofollow noreferrer">https://twitter.com/rajasimon</a> to get access.
What is your data and privacy policy? I'm a bit concerned not seeing anything when accessing such sensitive information. This is a non-starter for me.<p>Even if that was the case, the only authentication being through Google is another absolute blocker for me to using your service.<p>Also, your documentation loads extremely slows for me especially a single, static page of docs. That's clearly Notion's fault but isn't a great look.<p>I like the idea, but this definitely feels like it needs a lot of polish and feels more like a proof of concept than an actual product.