Delays & Debouncing - Bunnylynk Docs

Why Delay Webhooks?

In many real-world architectures, receiving a webhook immediately causes a race condition:

A Stripe payment_intent.succeeded webhook fires before your checkout frontend completes creating the user record in your primary database.
Multiple rapid edits in Shopify trigger 10 back-to-back products/update events within 2 seconds.

You can configure a Connection to hold events for a set number of seconds before initiating the first delivery attempt:

{
  "rules": {
    "delay_seconds": 30
  }
}

The event is ingested instantly (sender gets 200 OK in 15ms), but Bunnylynk waits 30 seconds before executing the HTTP dispatch to your server.

Debouncing collapses multiple updates for the same entity into a single delivery.

{
  "rules": {
    "debounce": {
      "key": "body.data.object.customer_id",
      "window_seconds": 60,
      "strategy": "last_wins"
    }
  }
}

If 5 updates for customer cus_12345 arrive within 60 seconds, Bunnylynk buffers them and only delivers the final payload once the window closes.