I built a small tool to help debug and inspect webhooks more easily. It gives you a unique URL where you can see incoming requests, headers, payloads, and even replay them.
Built in Go, it’s lightweight, open source, and free to use.
It can receive per board and global webhooks about what is happening at WeKan kanban boards, and run python code https://github.com/wekan/wekan/blob/main/api.py to use WeKan API to do some change at WeKan.
Looks great, I needed something like this recently.
Any chance of doing full support for serverless platforms with scale-to-zero? Test infrastructure is usually a great fit for serverless since their usage looks like CI runners - high spikes when tests are running and 0% utilization otherwise.
So I’ve been looking at these sorts of tools recently as am building webhooks into my project. One common theme is that none of them allow you to change/add the response headers; only the body.
Otherwise it looks good! If you add the above I will have a reason to stop looking!
Would love your feedback on a tool I am making that I think does exactly that. Still alpha, but would appreciate any feedback on if this solves your problem
tl;dr: configure responses to your 3rd party http dependencies, matching against header or body or url, and returning a custom response, including headers.
The best feature, I think, is that you can pass a header in that configures the response, so you can have tests that dynamically force response content/errors. That and allowing your integration tests to validate error paths and various states.
I built a small tool to help debug and inspect webhooks more easily. It gives you a unique URL where you can see incoming requests, headers, payloads, and even replay them.
Built in Go, it’s lightweight, open source, and free to use.
Try it out: https://testwebhook.xyz
Code: https://github.com/muliswilliam/webhook-tester
Would love your feedback or suggestions!
This post falls under Show HN and should probably follow the guidelines (eg. title should begin with Show HN:). See https://news.ycombinator.com/showhn.html
Tool itself looks interesting and I've been looking for something like this several times. I'm bookmarking it for next time.
Thank you, I will post it in show HN
Here is PHP webhook receiver:
https://github.com/wekan/webhook/blob/main/public/index.php
It can receive per board and global webhooks about what is happening at WeKan kanban boards, and run python code https://github.com/wekan/wekan/blob/main/api.py to use WeKan API to do some change at WeKan.
https://wekan.github.io
https://github.com/wekan/wekan
https://github.com/wekan/wekan/wiki at right menu is more info about webhooks etc
Looks great, I needed something like this recently.
Any chance of doing full support for serverless platforms with scale-to-zero? Test infrastructure is usually a great fit for serverless since their usage looks like CI runners - high spikes when tests are running and 0% utilization otherwise.
Probably not hard to wrap this in a docker image and throw it into GCP as cloud run
Would probably need to change the code to get rid of the generated url part though
So I’ve been looking at these sorts of tools recently as am building webhooks into my project. One common theme is that none of them allow you to change/add the response headers; only the body.
Otherwise it looks good! If you add the above I will have a reason to stop looking!
I'm pretty sure Wiremock (https://wiremock.org) lets you configure both the response body and headers.
Thank you for the feedback. I will add a feature to customize response headers today.
Any other features you would like to see in the app?
Honestly no… testing them needn’t be a complex process!
There is another service that allows for scripting which I’m sure some people love, but I just need somewhere I can set the response.
Would love your feedback on a tool I am making that I think does exactly that. Still alpha, but would appreciate any feedback on if this solves your problem
https://voodoocall.com/docs/
tl;dr: configure responses to your 3rd party http dependencies, matching against header or body or url, and returning a custom response, including headers.
The best feature, I think, is that you can pass a header in that configures the response, so you can have tests that dynamically force response content/errors. That and allowing your integration tests to validate error paths and various states.