Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

The Real-World Pain

Описание и применение

Проблема: вебхуки от Stripe, Meta и CRM исчезают на самодостаточных n8n за Cloudflare. Решение: разделить прием и обработку, добавить HMAC‑проверку и ключи идемпотентности, настроить таймауты прокси.

Задача

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.

Результат

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

Рабочий процесс

  • 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.

Доказательства

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

Источник

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.

Источник

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

Источник

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

Источник

  • Дата записи: 2026-11-02T18:14:15.287Z