Batch process data with Redis-powered debouncing system
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 15 nodes and runs when another workflow calls it. Along the way it connects Redis.
How it runs
Trigger: When another workflow calls it.
- Get lock value (Redis): get
- Is lock active? (If): checks a condition and branches into true / false
- Wait: waits 1 seconds
- Push to message list (Redis): push
- Crypto: hashes or encrypts values
- Set last update uuid (Redis): set
- Wait: waits 2 seconds
- Get last update uuid (Redis): get
- Am I last? (If): checks a condition and branches into true / false
- Set lock (Redis): incr
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Crypto
n8n-nodes-base.crypto - Redis
n8n-nodes-base.redis - If
n8n-nodes-base.if - Wait
n8n-nodes-base.wait - Split Out
n8n-nodes-base.splitOut - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger
From the author
How it works This implementation aggregates incoming data into a Redis list from potentially concurrent workflow executions. It buffers the data for a set period before a single execution retrieves and processes the entire batch. Step-by-step Flow: 1.…