n8n Instagram & WhatsApp Webhook to CRM w/ Retries & Dedupe

Stop duplicate CRM leads from social webhooks—retry safely, log everything

This n8n workflow receives Instagram or WhatsApp-style webhook events, creates a deterministic SHA-256 idempotency key to prevent duplicates, forwards valid messages to your CRM via HTTP, retries transient failures with backoff, and records every delivery outcome in an n8n Data Table—while preparing alerts for permanent failures.

What this workflow does

• Receives events: Exposes a POST webhook endpoint for incoming Instagram/WhatsApp webhook payloads.
• Normalizes & validates: Converts the incoming JSON into a consistent format, checks required fields, and immediately finalizes invalid payloads.
• Deduplicates with SHA-256: Generates a deterministic SHA-256 idempotency key and skips events already seen to avoid duplicate CRM entries.
• Routes only new, valid items: Sends only deduped, valid events onward; duplicates are finalized right away.
• Delivers to CRM with classification: Sends the event to your CRM webhook URL using HTTP and classifies results as:
  • Delivered: 2xx responses
  • Permanent invalid: 4xx responses
  • Retryable: other responses and/or timeouts
• Retries with progressive backoff: Retries retryable deliveries with waits of 1, 5, and 15 minutes, up to three total attempts.
• Ledger + reprocessing flag: Upserts a record into an n8n Data Table including payload, HTTP status, attempts, and a reprocessing flag.
• Alerts for failures: Formats an alert message for failed or permanently invalid outcomes so you can connect an alert step (e.g., Slack/email) as needed.

Use cases

• Preventing duplicate lead creation when Instagram/WhatsApp webhook retries occur.
• Reliably pushing inbound messages to a CRM endpoint during intermittent downtime (with backoff retries).
• Building an audit trail of every webhook delivery attempt in an n8n Data Table.

Technical details

• Webhook intake: POST webhook endpoint
• Nodes/logic: if, set, code, no op, wait, switch
• CRM integration: HTTP delivery to crm_webhook_url (Config node)
• Data storage: Upsert to an n8n Data Table ledger (payload, HTTP status, attempts, reprocessing flag)