Redis locking for concurrent task handling
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 14 nodes and runs when an HTTP GET request hits its webhook URL. Along the way it connects Redis.
How it runs
Trigger: When an HTTP GET request hits its webhook URL.
- Fetch Webhook Data & Declare lockValue (Code): runs custom JavaScript code
- Check Redis Lock (Redis): get
- redisLock existence boolean (If): checks a condition and branches into true / false
- Acquire Redis Lock (Redis): set
- redisLock acquired booleans (If): checks a condition and branches into true / false
- Workflow Switch (Switch): routes items into 3 branches
- Poll for lock (Wait): pauses before continuing
- Workflow (Edit Fields (Set)): sets or maps fields
- Workflow (Edit Fields (Set)): sets or maps fields
- Workflow (Edit Fields (Set)): sets or maps fields
…plus 2 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 (8)
- No Operation, do nothing
n8n-nodes-base.noOp - Edit Fields (Set)
n8n-nodes-base.set - Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - Redis
n8n-nodes-base.redis - If
n8n-nodes-base.if - Wait
n8n-nodes-base.wait - Switch
n8n-nodes-base.switch
From the author
👤 Who is this for? This workflow is great for n8n users who want to prevent duplicate or overlapping workflow runs. If you're a developer, DevOps engineer, or automation enthusiast managing tasks like database updates, syncing tools, or hitting rate-limited…