From solo developers monitoring side projects to teams routing events across services. If a webhook needs to be received, inspected, transformed, or delivered, Dispatch fits.
Five lanes. If yours isn't here, the generic webhook destination probably covers it.
Manage many repos without managing many bots. One endpoint per project feeds pushes, PRs, CI results, and releases into a single dashboard, routed to the right channels.
details ↓Feed live events into Dispatch while you build. Inspect the full payload, see exactly what the provider sends, and replay events as many times as you need.
details ↓Failed invoice, disputed payment, high-severity error: route the events that matter to the people on call, and log the quiet ones without paging anyone.
details ↓One inbound event, many destinations. Send GitHub to #dev and Jira to #product, or deliver the same event to Discord, Slack, and your own API at once. No custom bots.
details ↓Put Dispatch in front of your API as a normalization layer. JSONata transforms reshape every provider's payload into the one format your system expects, before any of it reaches your code.
details ↓Integration development
Building a new integration means waiting for the right event to fire, inspecting the payload, realizing something is wrong, fixing it, and waiting again. That cycle is slow.
Dispatch stores every inbound event with its full payload. Inspect headers and body in the dashboard, see exactly what the provider sent, and replay the event to any destination as many times as you need. The source system never knows.
{
"action": "opened",
"number": 482,
"pull_request": {
"title": "fix: retry jitter",
"user": { "login": "ari" }
}
}
Repo & project monitoring
Maintaining many repos means a constant context switch: per-repo Discord bots, duplicated webhook configs, notifications scattered across channels.
Dispatch gives you one endpoint per project. Pushes, pull request reviews, CI status, and releases flow through the same pipeline, routed to the right channel and formatted consistently, with a full event log when something needs an audit.
Alerting & on-call
Webhook noise is real. Most events aren't worth a notification, and the one that is can't drown in a channel nobody reads.
Filter rules decide which events page your team and which just get recorded. Critical payment and error events hit the on-call channel; routine ones land in a quiet log, stored and searchable.
body.level in ("error", "fatal")
body.project eq "payments-api"
Event routing & fan-out
Delivering one event to several places usually means custom bots, duplicated webhook configs, or a glue service you now maintain.
Dispatch links any number of destinations to an endpoint and fans out every event to all of them. Each destination gets its own template, retry policy, and delivery log.
API & integration middleware
Every provider sends webhooks differently. Stripe wraps everything in an envelope. GitHub sends a different flat shape per event type. Jira nests everything. Adapter code for each one is complexity your API doesn't need.
Dispatch sits in front of your API. JSONata transforms reshape each provider's payload into one consistent format before it reaches your code. Your API sees one clean schema, not twelve.
Provider sends
{
"type": "invoice.payment_failed",
"data": {
"object": {
"id": "in_1QkX9w",
"amount_due": 4900
}
}
}
Your API receives
{
"event": "payment.failed",
"invoice": "in_1QkX9w",
"amount": 4900
}
Set up your first endpoint in minutes. Free to start, no credit card required.
POST /hooks/your-slug