Dispatch relaunch — webhook ingress, routing rules, and CLI tunnel (dispatch listen)
Hey PH — Ari here. Dispatch is a team effort with @evan_goldberg.
We shipped an early version a while back. Since then we rebuilt almost everything around one annoying truth: teams keep rewriting the same webhook plumbing, and nobody wants to own it.
What Dispatch does
One URL receives webhooks from your providers
Per-provider signature verification (GitHub, Slack, Stripe, GitLab, Linear, Jira, Bitbucket, PayPal, plus custom HMAC)
Filter events using header/body conditions before anything delivers
Transform payloads with JSONata (no JS sandbox, no eval)
Templates that match where messages land: Discord embeds, Slack Block Kit, Telegram HTML, plus generic HTTP
Retries with backoff, replay/history, and delivery visibility so debugging isn’t guesswork
What’s new in this relaunch
dispatch listen 3000 — tunnel live production webhooks to localhost over WebSocket (less public-URL hassle for local dev)
Routing rules — one endpoint can pick different templates, transforms, or destinations based on payload
Template editor with live preview (especially for Discord formatting)
Demo video: https://youtu.be/TziIp9NXF24
Feedback we actually want
After reading the homepage, what category do you put us in (webhook infra vs automation vs notifications) — and is that wrong?
What’s the #1 question the homepage doesn’t answer that would block you from trying it?
Want to stress-test the CLI tunnel? Reply “tunnel” and we’ll DM a Pro comp.
Thanks for taking a look.
Replies