Webhook events belong in an inbox, not a terminal scrollback.

Hooook gives every workflow a webhook channel, turns incoming payloads into readable events, and pushes the important ones to your iPhone.

Channels
one URL per workflow
Inbox
web and iOS
State
unread to resolved
Hooook web dashboard showing webhook channels, events, and event detail
Hooook mobile dashboard showing the webhook inbox

Built for the messy middle after a webhook fires.

Webhook tools are good at catching requests. Hooook focuses on what happens next: who saw it, what it means, and whether it needs action.

A channel for every workflow

Give Stripe, GitHub, CI, cron, and internal jobs their own webhook URL so every event lands with clear ownership.

Payloads you can read quickly

Turn raw JSON into readable Markdown, event summaries, and searchable detail without losing the original request.

Push the right events to iOS

Send urgent hooks to your phone while keeping routine noise in the web inbox for later triage.

Unread, acked, resolved

Track lightweight incident states across a team instead of letting important callbacks disappear into logs.

A calmer loop for callback-driven work.

Keep the developer speed of a temporary webhook URL, then add the team affordances that make events actionable.

01

Capture

Create a channel and paste its URL into any webhook sender.

02

Triage

Read the normalized event, inspect payload detail, and add context.

03

Notify

Escalate the events that should interrupt you on iPhone.

04

Resolve

Ack, replay, or close the loop once the workflow is handled.

One inbox for the hooks that currently vanish into Slack, logs, and memory.

Route each source to a named channel and keep the event history close to the people who need to act on it.

Build alerts

Deployments, CI failures, preview URLs, and release jobs.

Payments

Failed invoices, disputes, refunds, and subscription lifecycle hooks.

Customer ops

Forms, support automations, CRM callbacks, and onboarding events.

Scheduled jobs

Cron results, backup status, sync drift, and health checks.

Start with the webhook URL you already need.

Create a channel, paste the URL into any provider, and watch events appear in the dashboard before deciding which ones deserve a phone notification.

Create channel
curl -X POST https://api.hooook.dev/api/channels/prod/events \
  -H "content-type: application/json"   -d '{
    "source": "stripe",
    "type": "invoice.payment_failed",
    "priority": "high"
  }'

Give your next webhook a place to land.

Open the dashboard, create a channel, and turn the next callback into an event your team can actually close.

Open dashboard