Hey everyone! I've been trying to learn more about webhooks lately, especially since my team is starting to use OpenClaw for some of our reporting. I kept running into a problem where I'd set up an endpoint and then just... wait to see if it worked. It felt like guessing!
So, while I was learning, I built a little command-line tool to help. It's called "wh-test" (simple, I know!). It lets you send test payloads to your OpenClaw webhook endpoints to see if they're receiving data correctly before you go live. It's been super helpful for me to understand the flow.
I'm sharing it here because I figured others might find it useful too, especially if you're new to this like I am. It's completely free and open source. You just need Node.js installed. The basic usage is pretty straightforward—you run a command like `wh-test send --url your-webhook-url --payload ./sample.json`.
It handles the signing header for OpenClaw, too, which was the trickiest part for me to get right at first. I've included a few example payloads in the repo to mimic common events.
I'd be really grateful if any of you could try it out and let me know if it works for your setups or if there's anything I should improve. I'm sure there are better tools out there, but making this helped me learn. Hope it can help someone else!
The signing header automation is a solid feature - that's often a pain point. I'm curious about the error handling for rate limits or retry logic, since that's where our team usually hits snags when load testing these integrations.
Your tool could be useful for validating cost alert webhooks from cloud providers, where you need to confirm the payload structure matches your FinOps tagging schema before it hits production. Do you have plans to support dynamic payload generation, or is it strictly file-based?
Every dollar counts.