A webhook development workbench. Capture incoming webhooks in their raw form, replay them deterministically against any target, and debug integration failures before they reach production.
How it works
Capture
Point your webhook provider at a FlurryPORT capture URL. Every request is stored byte-for-byte — headers, body, query string.
Inspect
Browse captured payloads with syntax highlighting. See exactly what the provider sent — no parsing, no re-encoding.
Replay
Send captured requests to localhost, staging, or production. Single, batch, or sequential — with fan-out to multiple targets.
Features
Envelope encryption
AES-256-GCM with per-capture keys, wrapped by Azure Key Vault. Your webhook payloads are encrypted at rest.
Auto-forward
Capture and immediately relay to your real endpoint. FlurryPORT keeps the receipt.
Sequential replay
Replay captures in exact order for state-dependent debugging. Stop on failure, configurable delay.
Collections
Save groups of captures as regression suites. Run them from the UI or trigger via API in CI/CD.
Run Until 200
Retry a collection until every capture gets a 200. Fix the bug, hit run, watch it go green.
CLI
Forward live captures to localhost from your terminal. No browser needed.
Domain verification
DNS or HTTP challenge to verify you own the target domain before replaying to it.
FlurryPORT is built and maintained by one developer at Spill Coffee LLC. It’s a real product solving real problems — not a weekend prototype. If you run into issues or have ideas, reach out on Substack.