Understanding Meritto's Webhook Queue System

Understanding Meritto's Webhook Queue System

Overview

To ensure your data reaches external systems faster and more reliably, Meritto now uses two separate queues to manage webhook traffic: one for real-time updates and one for bulk data pushes.

Key Features

Real-Time Queue

What it handles:

  • Automatically triggered and manually done ( Single Push )  webhook events like lead verification, application submission, payment confirmation, application stage updates, etc., which have a record size of less than 10 records, are pushed via this Queue. 

How it works:

  • This queue processes data instantly as soon as the event occurs in the system.
  • Best suited for critical, time-sensitive updates that must reflect in your ERP without delay.

Definition:
An event is treated as real-time if it generates less than or equal to 10 webhook hits per second.

Bulk Queue

What it handles:

  • Manual uploads, large imports, or Bulk actions that make more than 10 records fall under the configured webhook events at once.

How it works:

  • This queue introduces a 5-minute delay before processing to prevent congestion.
  • It ensures real-time events are not blocked by large uploads or mass actions.

Definition:
An event is treated as bulk if it generates more than 10 webhook hits per second or is triggered by a bulk action (e.g., uploading thousands of leads or updating hundreds of applications at once).

Summary

Type

Definition

Queue Used

Processing Time

Real-Time≤10 Records or single eventReal-Time QueueImmediate (live sync)
Bulk>10 Records or bulk upload/updateBulk QueueFrom 5 mins to 30 mins

This structure ensures speed for urgent data and efficiency for large-scale operations, keeping your systems in sync without manual intervention or delay.