Please add optional HMAC signature validation directly inside the Inbound Webhook workflow trigger.

The Problem:

Many third-party platforms (payment processors, custom SaaS tools,etc) issue an HMAC key and send a signature header (e.g., X-Signature) to verify payload authenticity. Currently, HighLevel cannot validate header signatures on incoming webhooks. This forces users to route webhooks through middleware (Make, Zapier, or a custom server) just to verify the request before forwarding it to HighLevel.

Proposed Solution:

Add an optional HMAC Verification configuration block inside the Inbound Webhook trigger settings:

Secret Key Field: Input for the shared secret/HMAC key.

Header Name Field: Input to specify the signature header (e.g., X-Signature, X-Hub-Signature-256).

Algorithm Selection: Dropdown to select the hashing algorithm (e.g., SHA-256, SHA-1).

Behavior: Automatically reject or drop incoming requests if the computed signature does not match the header.

Why This Matters:

This would allow users to build secure, direct integrations with external tools without needing expensive third-party middleware or custom code servers.