Skip to content
HookDeploy
HookDeployDocumentation
On this page ↓
Getting startedIntroduction

What HookDeploy is, who it's for, and the core concepts behind webhook capture and replay.

→Getting startedQuickstart

From signup to your first captured webhook in under five minutes.

→Getting startedYour first endpoint

Create an endpoint, copy its URL, send test requests, and read the request inspector.

→Core conceptsForwarding

Forward captured webhooks to one or more destinations, with optional payload transformation.

→Core conceptsTransformations

Reshape webhook payloads before forwarding with the visual editor and 23 built-in formatters.

→Core conceptsEndpoint security

Restrict access to your HookDeploy endpoints with IP allowlists and secret token authentication.

→Core conceptsCustom Responses

Override the HTTP response HookDeploy returns to webhook senders. Set a custom status code, response body, and dynamic variables for testing and mocking.

→Core conceptsResponse Delay

Add an artificial delay before HookDeploy responds to a webhook sender. Useful for testing timeout handling and retry logic.

→
↑↓ navigateEnter openEsc close

Incidents

Correlate forward failures into incidents, triage with status and updates, and bulk-replay failed deliveries at a controlled rate.

Overview

An incident groups related forward failures so you can triage outages instead of chasing individual failed deliveries. HookDeploy opens an incident when forwards fail in a correlated pattern — either the same destination, or the same provider ASN (autonomous system) across destinations within a short window.

How correlation works

Failures attach to an existing open or investigating incident when they match:

  • Destination scope — the same forward destination keeps failing
  • Provider scope — failures share the same ASN (provider-level grouping) and the previous matching failure was within 30 minutes

If no open or investigating match exists, HookDeploy may open a new incident. When a new incident follows a recently resolved one with the same correlation key within 14 days, it is linked via previous_incident_id so you can see recurrence.

Statuses

StatusMeaning
OpenActive failure cluster. New matching failures continue to append.
InvestigatingSomeone is actively working the issue. Matching failures still append.
ResolvedTriage is complete. Matching failures no longer append; a later match may open a new (possibly recurring) incident.

Status changes are recorded on the incident’s Updates timeline as system notes.

Updates timeline

Each incident has a collaborative Updates feed. Any organization member can post notes (for example root-cause findings or next steps). Status transitions also write system updates automatically. Use the timeline to keep triage context with the incident rather than scattered across chat threads.

Bulk replay

From an incident you can queue a paced replay of unreplayed failures. You choose a requests-per-minute rate; HookDeploy spaces deliveries accordingly.

Plan availability

Creating, viewing, updating status, and posting updates have no plan gate — every plan can use incidents.

Bulk incident replay requires Starter or above. Free plans receive plan_limit if they call the replay API. This is separate from private tunnel access (Team+).

Where to work with incidents

  • Dashboard — Incidents list and detail (status, updates, replay)
  • REST API — Incidents API and Incident subscriptions
  • Zapier / n8n — triggers on created / investigating / resolved, plus update and replay actions