# Verify a Signed Webhook with Timestamp

Source: https://openflow.run/en/templates/verify-signed-webhook-with-timestamp/
Content language: en
Template revision: 6a810ce0d6451572951d8ffad4656467a01774f0

Developer Tools

Verify exact webhook bytes and a signed timestamp before accepting an event.

[Use in Open Flow](https://console.openflow.run/flows?importUrl=https%3A%2F%2Fraw.githubusercontent.com%2Foomol-lab%2Fawesome-workflow-templates%2F6a810ce0d6451572951d8ffad4656467a01774f0%2Fworkflows%2Fverify-signed-webhook-with-timestamp%2Ftemplates%2Fverify-signed-webhook-with-timestamp.openflow.json)

*   [Open Flow JSON](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/workflows/verify-signed-webhook-with-timestamp/templates/verify-signed-webhook-with-timestamp.openflow.json)
*   [n8n JSON](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/workflows/verify-signed-webhook-with-timestamp/templates/verify-signed-webhook-with-timestamp.n8n.json)

![Verify a Signed Webhook with Timestamp workflow in Open Flow](https://openflow.run/template-previews/verify-signed-webhook-with-timestamp/light.webp)

Verify exact webhook bytes and a signed timestamp before accepting an event.

## Setup

Apply body-size and rate limits at the ingress; the relay is subject to Open Flow input limits.

## Behavior

The sender signs the exact JSON bytes with HMAC-SHA256 and supplies X-Automation-Signature as sha256= followed by hexadecimal. The signed event\_id must start evt\_ and contain 8–64 letters, digits or hyphens. The integer sent\_at must be at most 300 seconds old or 60 seconds in the future. Accepted requests receive 200; invalid or stale requests receive a generic 401. Both responses include no-store and nosniff headers. The time window does not deduplicate repeated events; add persistent event-ID deduplication where needed.

In n8n

Configure a shared HMAC secret in the n8n Crypto credential. For Open Flow mode, bind WEBHOOK\_HMAC\_SECRET to the same secret, deploy its webhook, and configure the Open Flow relay URL in n8n. Activate only one n8n webhook and protect the relay endpoint.

Inspiration & credits

Adapted from [Signed Webhook HMAC Guard with Timestamp Window](https://github.com/enescingoz/awesome-n8n-templates/blob/827110332c21cbe000ab13f6d292d5adb1f1f8db/Other_Integrations_and_Use_Cases/Signed%20Webhook%20HMAC%20Guard%20with%20Timestamp%20Window.json) in [enescingoz/awesome-n8n-templates](https://github.com/enescingoz/awesome-n8n-templates).

Source collection notice: © 2024–2026 Enes Cingoz, [CC BY 4.0](https://github.com/enescingoz/awesome-n8n-templates/blob/827110332c21cbe000ab13f6d292d5adb1f1f8db/LICENSE). The source export does not identify a separate template author or license. See [repository licensing](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/README.md#licensing) for the scope of OOMOL contributions and third-party material.

## What you’ll need

*   Shared HMAC secret

*   webhook
*   hmac
*   security

[View on GitHub](https://github.com/oomol-lab/awesome-workflow-templates/blob/6a810ce0d6451572951d8ffad4656467a01774f0/workflows/verify-signed-webhook-with-timestamp/README.md)
