Skip to main content
The WEBHOOK channel triggers an HTTP POST request to the target HTTPS URL configured in the recipient field.

Secure Request Verification

To prevent spoofing or unauthorized posts, every webhook payload is signed with a cryptographic signature sent in the request header: x-notifyflow-signature This header contains an HMAC-SHA256 signature generated using a shared Webhook signing secret. You can set this secret in the Settings tab.

Verifying Webhook Signatures

To verify that the webhook request came from Notifyflow, compute the HMAC-SHA256 hash of the raw request body string using your shared secret, and compare it to the signature header.

Retries and Timeouts

  • Connection Timeout: Webhook workers enforce a 5-second response window. If the target server fails to reply within 5 seconds, the request is considered a failure.
  • HTTP Failure States: Any status code outside the 2xx range (such as 500 Internal Error or 404 Not Found) is treated as a delivery failure.
  • Retry Loop: Webhook failures undergo 4 automatic retries using exponential backoff before being marked as dead-letter events.

Developer Implementation

To dispatch webhook events, configure your recipient as the destination webhook listener URL, and pass the event payload in the data parameter: