Skip to main content
A destination is an HTTPS URL that gets events from a project. Each destination has its own queue, attempts and log.

​
Add a destination

Open Destinations → Add destination in your project.

​
The request that hooksnode sends

hooksnode builds the headers in this order. A later step replaces a header of the same name.
  1. The headers of the incoming request.
  2. The destination’s extra headers.
  3. X-Hooksnode-Source-Id: <source-id>.
  4. X-Hooksnode-Signature: sha256=<hex>, if signing is on.

​
Success and failure

  • A 2xx response is a success. hooksnode stores up to 1 MiB of the response body.
  • Anything else is a failed attempt. See Retries.

​
Test before you save

The destination editor has a Test panel. Paste a sample body. hooksnode runs your transform and filter and shows the output, whether the filter matched, and any error. Nothing is sent.

​
Health checks

Every 15 minutes, hooksnode sends a HEAD request to each destination, with a 5 second timeout. A 5xx or no answer is unhealthy. A 4xx is degraded. Anything else is healthy.

​
Limits