Running n8n, Make, Zapier, or a custom automation? You need a reliable webhook endpoint that stores payloads for processing — not a testing tool that disappears in 7 days. HookRelay gives you permanent webhook storage with full API access.
The problem: Most webhook testers expire. Most automation platforms charge per workflow. HookRelay gives you a permanent, free HTTP endpoint that captures any payload so your automation can process it on demand.
Use as a buffer between trigger sources and n8n workflows. Capture events even when n8n is paused.
HookRelay stores the webhook first, then your Make scenario polls and processes on schedule.
Use as a catch-all for webhooks before routing to the right Zap, or as a dead letter queue.
Perfect for AI agents that run on cron and need to check for new webhooks between runs.
Capture form or API events and review in HookRelay before syncing to your Airtable base.
Any script that can make a GET request can poll your HookRelay endpoint for new payloads.
You're processing Stripe payment events with an n8n workflow. The workflow sometimes gets overloaded or offline. If Stripe POSTs and nothing is listening, the event is lost.
Solution: Point Stripe at your HookRelay endpoint. It captures every event reliably. Your n8n workflow polls HookRelay every few minutes and processes the queue. No lost events.
You're running an AI agent that makes external API calls (image generation, video processing, data enrichment). These APIs send a webhook when the async job completes — but your agent is running in a Lambda or cron job that can't keep a connection open.
Solution: Give the external API your HookRelay endpoint as the callback URL. Your agent checks the endpoint on its next run and processes any completed jobs it finds.
# Agent run 1: kick off async job, give HookRelay as callback
curl -X POST https://api.imagegen.example.com/generate \
-d '{"prompt":"...", "callback":"https://hookrelay-app.netlify.app/api/webhook/YOUR_UUID"}'
# Agent run 2 (10 minutes later): check for completed jobs
curl https://hookrelay-app.netlify.app/api/webhook/YOUR_UUID/requests
[{"id":"req_001","body":{"status":"completed","image_url":"https://..."},"received_at":"..."}]
Your static site has a contact form. You want to collect submissions while you build your CRM integration. webhook.site would work but expires in 7 days — and you won't get the integration done in 7 days.
Solution: Set your form action to your HookRelay endpoint. Submissions are captured indefinitely. When your CRM is ready, you can batch-import everything stored.
<!-- HTML form — submissions go to HookRelay -->
<form action="https://hookrelay-app.netlify.app/api/webhook/YOUR_UUID" method="POST">
<input name="email" type="email" required>
<input name="message" type="text">
<button type="submit">Send</button>
</form>
Your main webhook handler occasionally fails (server restart, deploy, network blip). You want to catch any events that didn't get processed so you can replay them later.
Solution: Configure your webhook source with a fallback URL pointing to HookRelay. If your primary handler returns a 5xx, the source retries to HookRelay. You can inspect and replay the events when you're back online.
POST https://hookrelay-app.netlify.app/api/webhook/create
{"uuid":"YOUR_UUID","url":"https://hookrelay-app.netlify.app/api/webhook/YOUR_UUID","expires":null}
POST https://hookrelay-app.netlify.app/api/webhook/YOUR_UUID
Content-Type: application/json (or form-encoded, or XML)
{"status":"ok","id":"req_XXX"}
GET https://hookrelay-app.netlify.app/api/webhook/YOUR_UUID/requests
[{"id":"req_001","method":"POST","headers":{...},"body":{...},"received_at":"2025-03-19T..."}]
Most automation platforms (Make, Zapier, n8n) have built-in webhook triggers. They work well — but have real limitations for certain scenarios:
HookRelay is a dumb storage layer — it always accepts and stores. Your automation fetches from it when ready. Simple, reliable, decoupled.
Permanent storage for any webhook payload. Free tier, no account, no expiry.
Create Free Endpoint →