How to handle high webhook volume with business hours logic, avoiding scheduler bottleneck?

How To
,
1

I’m receiving real-time webhook requests (from Klaviyo flows) into Make. I need to send WhatsApp messages only during specific business hours (for example: 7:00–21:00, with variations on weekends).

Since Make doesn’t allow complex business-hour filters directly inside filters, I originally tried to solve this by using:
• Scheduled scenario: “At regular intervals” (1 min minimum)
• Sequential Processing OFF (to allow parallel processing)

However, even with Sequential Processing OFF, the scheduler only processes 1 bundle per interval, which creates a growing queue during busy hours.
Eventually, I face growing backlog and risk losing timely message delivery.

I want to:
• Trigger real-time execution for every webhook bundle (no delay)
• Apply business-hour filtering logic directly inside the scenario
• Avoid queue build-up and avoid sending batch messages at 7:00am
• Keep system stable at high volume (15+ flows sending webhooks)

My question:
• Can I apply business-hour logic inside the scenario using variables or functions that support more complex time checks?
• What is the recommended architecture for real-time webhook flows that need controlled sending windows?

2

Hey Vadim,

what type of trigger are you using? If possible, it should be set to instant with sequential processing OFF so it will process a request immediately as it arrives.

About the time check - you can add a filter that checks if the time {{now}} is after 7 AND before 21. If it is - send the message, if its not, store it somewhere. Then have a separate scenario process the stored messages each morning as needed.

Now about the stability - this will need to be tested and if needed you can add a small delay somewhere to prevent hitting rate limits and add break modules to retry something if a rate limit is hit.

1 Like