You know how everyone says "build what you know"? Well, I’ve been down the webhook rabbit hole before. I built Webhooks for Sheets, a Google Workspace add-on that generates free webhooks… but only for Google Sheets. This little side project got over >150k installs (no joke!), but here’s the thing: that’s a vanity number. If one person installs it as an admin in a big org, boom — the number goes up. But the real insight? It came from the emails I received.
I got tons of messages from users asking about missing features, bugs, and the challenges of the Apps Script ecosystem. For example, there’s the whole issue with not being able to set specific response codes. These were my real insights into the user base — and it made me realize that people are really just looking for a simple solution to log webhook data in the tools they already use.
People love simple solutions. They want to log webhook data to their tool of choice without paying $$$ to tools like Zapier or Make.com. So, I thought, why not build something that does just that?
I got tons of messages from users asking about missing features, bugs, and the challenges of the Apps Script ecosystem. For example, there’s the whole issue with not being able to set specific response codes. These were my real insights into the user base — and it made me realize that people are really just looking for a simple solution to log webhook data in the tools they already use.
People love simple solutions. They want to log webhook data to their tool of choice without paying $$$ to tools like Zapier or Make.com. So, I thought, why not build something that does just that?
And that's how Hooksy was born!