Webhooks, written by an agent
The agent writes your webhook glue. You review a YAML diff.
Describe the integration in one sentence. Hooksmith drafts the hook, tests it on a real payload, and deploys a URL.
Free: 5 hooks and 10,000 events a month. Compare plans
Hooksmith for Mac
Tunnel live webhooks to localhost with their original signatures, and get a menu bar alert when a delivery fails.
Verification
Signature checks for the senders you already use
Pick a preset and the verification is configured for you, including the challenge handshake some providers require. Anything else works with a generic HMAC, shared header or basic auth check.
- StripeStripe-Signature, 5 min tolerance
- GitHubX-Hub-Signature-256
- Metaincl. WhatsApp and the GET challenge
- ShopifyX-Shopify-Hmac-Sha256
- TwilioX-Twilio-Signature
- Standard WebhooksSvix, Resend
- Generic HMACheader or basic auth too
Ask for the change. Read the diff.
Tell the agent what should be different. It proposes an edit to the hooksmith/v1 file and the CLI shows exactly what changes against the deployed version. Approve it, or ask again. Nothing is authored in the browser.
The hook is a plain YAML file in your repo, so your own review process still applies.
"Also ignore test-mode events."
conditions: - if: type != "invoice.payment_failed" then: skip: trueAdded: + - if: livemode == falseAdded: + then:Added: + skip: trueFour commands to a live URL
Authoring and testing work offline. The cloud is only needed once you want a public URL.
Install the CLI
Installs bun first if it is missing.
terminalcurl -fsSL https://hooksmith.tech/install.sh | bash
Connect your account
Same email and password as the dashboard. Add --register the first time.
terminalhooksmith login
Describe the hook
The agent drafts the YAML. You review the live preview and approve.
terminalhooksmith init && hooksmith new stripe-failed-payments
Deploy
Prints your /h/<id> URL. Paste it into the sender's webhook settings.
terminalhooksmith deploy stripe-failed-payments
Watch it arrive
Point a sender at the URL, or send a test event from the hook page. Events, request and response show up in the dashboard.
Start free
When something breaks, start from the event
Every request is recorded with the payload that arrived, what was sent to each destination, and what came back. Replay it once the fix is deployed.
Sample dashboard data: an event list and the selected event's details. Not interactive in this preview.
- Filter and search
- By status, hook, source or free text, with the current view kept in the URL so you can share it.
- Per-destination attempts
- Status code, duration, attempt count, and the exact request and response body for each destination.
- Replay with a confirmation
- Send a stored payload through the hook again as a new event. You see what will happen before it does.
- Send a test event
- Post your own JSON through a hook from the dashboard, without touching the sender.
What happens when a webhook arrives
Specific on purpose, so you can decide whether it fits your system.
The runtime does
- Verifies the sender's signature before anything else runs.
- Evaluates your conditions, renders the transform and calls every destination.
- Answers the sender as soon as the event is stored, then delivers in the background from a durable queue.
- Retries network errors, timeouts, 5xx and 429 on a schedule from 30 seconds to 24 hours (or the policy in your YAML), honouring Retry-After. Other 4xx fail at once.
- Drops duplicates that carry the same provider delivery id within 24 hours.
- Refuses destinations on private networks and does not follow redirects.
- Mutes or defers delivery during quiet hours, then sends the original payload.
- Records the event, its payload (unless you turn that off) and every attempt with status and timing.
- Replays any event whose payload was kept.
The runtime does not
- Guarantee ordering between events.
- Keep retrying forever. When the schedule is used up the delivery is marked failed; retry it or replay the event once the cause is fixed.
- Act as a message broker: there is no dead-letter queue or fan-in.
- Let you edit a hook in the browser. Changes go through the CLI or an agent, as a diff.
Every command is also an MCP tool
Point Cursor, Claude or any MCP client at the CLI. The agent can create, test, deploy and repair hooks without leaving the conversation, and you still approve each change as a diff.
hooksmith mcp serve
- list_hooks
- get_hook
- generate_transform
- create_hook
- edit_transform
- test_hook
- deploy_hook
- list_events
- replay_event
- fix_with_agent
- get_usage
Your next webhook takes one sentence
The free plan covers 5 hooks and 10,000 events a month.