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

Private Delivery

Team+

Deliver captured webhooks to private services over Tailscale without exposing them to the public internet.

Private delivery sends captured webhooks to services reachable through your Tailscale network. Use it when a destination should remain private rather than accepting inbound traffic from the public internet.

Private delivery vs public HTTPS

Standard forwarding delivers to a public https:// URL. Private delivery instead targets a service available through Tailscale, such as an internal hostname or private address and port.

Both destination types use the normal HookDeploy forwarding workflow: configure a destination, receive per-attempt status in request details, and use the destination’s retry controls. Standard public HTTPS forwards use a 15-second delivery timeout.

Customer setup

  1. Confirm the target service is reachable within your Tailscale network.
  2. In the HookDeploy dashboard, open the endpoint’s forwarding settings.
  3. Add a private destination and follow the displayed Tailscale connection instructions.
  4. Enter the private service address and port.
  5. Test the destination before relying on it for production traffic.

Keep access controls on the destination service enabled and grant only the network access required for webhook delivery. HookDeploy support can help validate configuration, but you remain responsible for your Tailscale network and service permissions.

Availability and pricing

Private delivery is available on Team and higher plans. Team includes one Tailscale tunnel. Additional tunnels are available for $19 per month each. Check the dashboard or current pricing page for the options available to your organization.

Next steps

  • Forwarding — Destination behavior, retries, and result tracking
  • Endpoint security — Stored payload protection and organization isolation