- Fire up ngrok to expose your local port
- Open webhook.site to see if Stripe or WhatsApp actually hits you
- Run an eternal curl to replicate the request
- Get lost in a sea of scattered logs or text files
β
It works. We've all done it for years.
β But let's be honest: it's chaotic, fragmented, and a massive time sink.
I always felt there should be a tool that centralizes this whole workflow, runs 100% on your own infrastructure, and respects privacy.
Since I didn't find one⦠I built it.
π₯ HookShot β
Open Source β built for devs who deal with webhook chaos daily.
If you work with:
Β· APIs & enterprise integrations
Β· Complex automations (n8n, Make, Odoo)
Β· Payment gateways & webhooks (Stripe, GitHub, WhatsApp Business)
HookShot gives you:
πΉ Total inspection β receive and analyze payloads in real time
πΉ HTTP control β simulate real environments with custom responses
πΉ Forwarding & replay β redirect events to localhost and replay requests with one click (bye bye, testing webhooks from external platforms)
πΉ Self-hosted β spin it up anywhere with Docker in seconds
π§ͺ The project is in its early, beautiful stage.
Your feedback can directly shape the roadmap.
If you build integrations and have 5 minutes to break it, clone it, or try it β I'd love to know:
- What key feature is missing to replace your current workflow?
- Was anything confusing when spinning up the container?
- What's your biggest webhook pain point that HookShot doesn't solve yet?
π Links in the first comment π
Top comments (1)
Here are the project links β any feedback is pure gold! π
π Landing Page: j-o-s-eandres.github.io/hookshot/
π» GitHub Repo: github.com/J-o-s-eandres/hookshot
If you like the idea or it saves you some time in your daily workflow, a βοΈ on the repo helps massively with visibility in the open source community.
Thanks, and happy debugging! π