Failed webhook retry (button or queue)

Ideas and Feature Requests
1

My idea comes from pardot / salesforce.
When pushes (webhooks) to remote systems fail in other systems It automatically retries.
But not after a fixed amount (because when the endpoint comes back up it would immediately go down again with all the retries).
This is why it would do exponential backoff.
Retry after 1 min / 1 hour / 1 day / failed

I think these groups of people would benefit from this idea:
Existing salesforce/pardot users

Why I think they would benefit from this idea:

  • Feature parity
  • It makes sense to have the webhooks retry when failed
  • Also now you dont see it when webhooks fail, I think we should notify the user.

Any code or resources to support this idea:

Are you willing to work on this idea?: yes

What skills and resources do you need to explore this further?
Not sure.

i’d suggest

  1. Guzzle backoff retry (if not there already)
    Backoff retry plugin — Guzzle documentation
  2. A button to manually retry a failed call
  3. A notification to the user when >1 request failed in the last minute. (X Webhooks failed in the last hour) SO you can go click it when the backend is up again.
2

Hello Frederik,

thanks for this idea.
I’m using Mautic webhook heavily with n8n / SuiteCRM and other system integrations.
The current fire and forget approach is simple and works as long as everything works.

Especially with customer data in external systems (CRM / CDP) and external calculations / logic implementations / workflows, a solid integration is required.
Integration monitoring as well - it’s best to proactively fix things and not hear issues from your customers feedback (or read about it on review pages / social meadia).

To start super simple, I’d start with your suggestions 2 & 3.
For 2: Where would you see the button? The queue would need to be enabled and there needs to be a visualization of the queue in order to see failed attempts and manually retry them?

As for 1: A queue and retry mechanism would be great. Probably best to split up this part since this could be a project in itself.

3

Screenshot 2025-12-02 at 08.35.19
Screenshot 2025-12-02 at 08.35.192196×1054 218 KB
I was thinking on this screen to add a button to retry it (that would be a first attempt)?

I was reading more and apparently guzzle has a sort of retry mechanism built in. Perhaps we already have this implemented without knowing?

4

The code that does the post:

Example Middleware for doing retries automatically