This workflow demonstrates a robust method for preventing simultaneous executions of workflows in n8n by leveraging Redis-based locking. It is designed to handle webhook-triggered events while ensuring that only one process handles a specific request at a time, avoiding conflicts and race conditions.
**Workflow Steps:**
1. An Incoming Webhook node listens for external triggers. When activated, it captures the webhook data.
2. The JSON parsing node extracts specific variables from the webhook payload and constructs a lock value.
3. The workflow checks Redis for an existing lock key (‘xyz-lock’) to determine if another process is running.
4. If no lock exists, it sets a new lock in Redis with a TTL (time-to-live) to prevent deadlocks.
5. It then uses a switch node to route the process based on the lock’s existence or success.
6. If the lock is acquired, the workflow proceeds; if a duplicate request is detected, it skips the process.
7. After completing its task, the workflow releases the lock by deleting the Redis key.
8. Sticky notes provide contextual explanations within the workflow for clarity.
**Use cases:**
This setup is ideal for scenarios where multiple webhook hits might trigger concurrent workflows, such as automating responses to form submissions, API calls, or chat responses, ensuring only one operation executes at a time to maintain data integrity and reliability.
Reviews
There are no reviews yet.