Skip to main content

Documentation Index

Fetch the complete documentation index at: https://supahooks.ar27111994.dev/llms.txt

Use this file to discover all available pages before exploring further.

When forwardUrl is configured, every request captured by your webhook endpoint is automatically forwarded to that destination as a POST request. This lets you route live traffic to another server — such as a staging environment, a data pipeline, or a second integration — while still capturing and inspecting the full event in the debugger. Forwarding happens automatically on every capture. If you want to resend a specific historical event to a target on demand, use replay instead.

​
Configuration

Set forwardUrl in your actor input to enable forwarding: 
{
  "forwardUrl": "https://example.com/ingest",
  "forwardHeaders": true,
  "maxForwardRetries": 3
}
​
forwardUrl
string
Destination URL that receives a copy of every captured request. Leave unset to disable forwarding.
​
forwardHeaders
boolean
default:"true"
When enabled, the original request headers are included in the forwarded request. Disable this to send only Content-Type and Content-Length, keeping the outbound request clean.
​
maxForwardRetries
integer
default:"3"
Maximum retry attempts for a failed forward request. Accepted range: 0–10.

​
Circuit breaker protection

To prevent a slow or failing downstream server from backing up your captures, forwarding uses a circuit breaker. After 5 consecutive failures, the circuit trips and forwarding is paused for 30 seconds. During that window, incoming webhook requests are still captured normally — forwarding resumes automatically when the pause expires.

​
Self-referential loop protection

Pointing forwardUrl at one of your own webhook endpoints would create an infinite loop. The runtime detects this and returns 422 Unprocessable Entity instead of forwarding the request.

​
Forwarding vs. replay

ForwardingReplay
TriggerAutomatic on every captureManual, per event
TargetFixed forwardUrlAny URL you specify at call time
RetriesmaxForwardRetriesreplayMaxRetries
Use caseMirror all traffic to a downstream serverResend a specific event to test a fix

​
Pairing with alerts

Combine forwarding with alertOn to get notified when delivery to your downstream server fails: 
{
  "forwardUrl": "https://example.com/ingest",
  "forwardHeaders": true,
  "maxForwardRetries": 3,
  "alertOn": ["error", "5xx"]
}
Generated webhook URLs are public unless you enable authKey, allowedIps, or signature verification. When forwarding to a sensitive downstream server, make sure your endpoint is secured before pointing production traffic at it.