The Real-World Pain

Description and use

Problem: Webhooks from Stripe, Meta, and CRM vanish on self‑hosted n8n behind Cloudflare. Solution: decouple ingestion and processing, add HMAC verification and idempotency keys, and harden proxy timeouts.

Problem

Inbound webhook payloads from Stripe, Meta WhatsApp, or CRM endpoints vanish on self-hosted n8n instances behind Cloudflare tunnels or reverse proxies, causing missed executions and false‑positive statuses.

Outcome

Webhook payloads are reliably received, processed idempotently, and proxy timeouts are eliminated, preventing missed executions and duplicate actions.

Workflow

• Create a lightweight ingestion workflow with a Webhook node that immediately validates the signature and responds 200 OK.
• Push the raw payload to a message broker or queue (Redis list or internal database).
• Trigger a secondary workflow via a Schedule or Queue Trigger to process items asynchronously.
• Use a Code node to compute an HMAC SHA‑256 hash, check a Redis cache for duplicate event IDs, and store processed IDs with a 24‑hour TTL.
• Harden Docker and Cloudflare/ngrok configurations by explicitly setting execution timeouts and correct binding parameters in docker‑compose.yml.

Evidence

Inbound webhook payloads from Stripe, Meta WhatsApp, or CRM endpoints simply vanish.

Source

Create a lightweight "Ingestion Workflow" whose only job is to validate the webhook signature, return an immediate 200 OK to the sender, and push the raw payload directly into a message broker or queue.

Source

Use a Code Node immediately following your webhook entry point to compute an HMAC SHA-256 hash using the provider's secret.

Source

Ensure your docker-compose.yml explicitly defines execution timeouts and correct binding parameters.

Source