My use case:
I use webhook triggers in workflows that depend on real-time communication (e.g., receiving messages from Telegram or Stripe events). If the n8n instance is restarting or momentarily overloaded, some webhook requests get dropped, and the workflow never runs. This creates data loss and unreliable automation.
I think it would be beneficial to add this because:
It would make webhook-based workflows more fault-tolerant and reliable, especially in self-hosted environments. This is important for users who rely on n8n in production and can’t afford to lose incoming webhook data due to short outages or restarts.
Any resources to support this?
- Telegram Bot API – Webhook Retry Behavior
- Stripe Webhooks – Retry Logic
- Some external tools like Nginx or message queues can do this manually, but it would be much more powerful and user-friendly if built into n8n directly.
Are you willing to work on this?
Not at the moment, but happy to test and give feedback if this gets added.Preformatted text