How do I batch incoming webhook messages for 3-5 seconds before processing

Questions
1

How do I batch incoming webhook messages for 3-5 seconds before processing

2

Hi @Anjali_sharma Welcome!
Each webhook call is its own execution, so a single run can’t natively “wait” for the next messages. The reliable pattern is a debounce backed by external state (Redis): on every incoming message, append it to a Redis list keyed by the sender/session, write the current execution’s ID to a marker key, Wait 3 to 5 seconds, then check the marker. If it still holds your execution ID, no newer message arrived, so this run pulls the whole list, clears it, and processes the batch. If the marker changed, a newer message took over, so this run just exits. Order of nodes

  1. Webhook
  2. Redis (RPUSH the message onto a per-session list key)
  3. Redis (SET a “last execution” key to {{ $execution.id }})
  4. Wait (3 to 5 seconds)
  5. Redis (GET the “last execution” key)
  6. If ({{ $json.value }} equals {{ $execution.id }})
  7. true branch: Redis (LRANGE to read all, then DEL the list) and process the batch; false branch: do nothing

There’s a ready-made template that implements exactly this debounce: