🔒 This workflow demonstrates Redis-based locking to prevent concurrent execution of workflows.
Configured with Redis, Switch, Wait, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Routing
- Transform
- Trigger
- Code
- Data store
- Wait
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| END | Routing | No Op | See node parameters |
| Workflow 1 | Transform | Edit Fields | See node parameters |
| Workflow 2 | Transform | Edit Fields | See node parameters |
| Workflow 3 | Transform | Edit Fields | See node parameters |
| Incoming Webhook Data | Trigger | Webhook | See node parameters |
| Fetch Webhook Data & Declare lockValue | Code | Code | See node parameters |
| Check Redis Lock | Data store | Redis | get |
| Acquire Redis Lock | Data store | Redis | set |
| redisLock existence boolean | Routing | If | See node parameters |
| redisLock acquired booleans | Routing | If | See node parameters |
| Poll for lock | Wait | Wait | See node parameters |
| duplicateWebhook boolean | Routing | If | See node parameters |
| Discard Redis Lock | Data store | Redis | delete |
| Workflow Switch | Routing | Switch | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
redis
Workflow notes
🔒 This workflow demonstrates Redis-based locking to prevent concurrent execution of workflows.
🔒 This workflow demonstrates Redis-based locking to prevent concurrent execution of workflows.
Steps:
- Try to acquire a lock via Redis
- If successful, execute workflow
- If duplicate request; ignore request
- Release the lock after completion
Sticky Note1
Attempts to acquire a lock using Redis by setting a key with expiration.
Sticky Note2
Skips execution when duplicate request is received.
Sticky Note3
Deletes the Redis lock key to release the lock.
🔒 This workflow demonstrates Redis-based locking to prevent concurrent execution of workflows.
🔒 This workflow demonstrates Redis-based locking to prevent concurrent execution of workflows.
Purpose and structure
This folder contains the 🔒 This workflow demonstrates Redis-based locking to prevent concurrent execution of workflows. workflow. Its executable nodes use code, if, noOp, redis, set, switch, wait, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Incoming Webhook Data
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0831_Wait_Code_Monitor_Webhook.json MIT; preserve source notices.