Prevent duplicate processing with Redis item state tracking
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 17 nodes and runs when another workflow calls it (plus 1 other trigger). Along the way it connects Redis and Google Sheets.
How it runs
Trigger: When another workflow calls it (plus 1 other trigger).
- Set: Context for Response (Edit Fields (Set)): sets 4 fields: fullKey, itemId, TTL…
- Parse Log Message (Code): runs custom JavaScript code
- Switch: routes items into 4 branches
- redis-audit-log (Google Sheets): append
- Redis: get
- Redis: set
- Redis: delete
- Redis: set
- Handle Invalid Action (Stop and Error): stops the run with an error
- Set CHECK Output (Edit Fields (Set)): sets 3 fields: success, isMember, itemId
…plus 5 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)
- Stop and Error
n8n-nodes-base.stopAndError - Edit Fields (Set)
n8n-nodes-base.set - Redis
n8n-nodes-base.redis - Switch
n8n-nodes-base.switch - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Redis Trigger
n8n-nodes-base.redisTrigger
From the author
I built this tool because we faced a real, recurring problem: managing hundreds of client projects in a weekly automated loop. There was a time when a single error in that process could create a complete data mess, forcing us to manually clean and re-run…