Hello, my workflow is working perfectly but i only want one thing, how to make a queue node that lets one user execute and let the others wait. Is there any node like this?
1 Like
There’s no dedicated “queue node” in n8n, but you can achieve this reliably with built-in patterns.
The simplest approach is to use a Wait + static data lock. Store a flag in workflow static data or an external store (Redis, DB). When a run starts, check if the lock exists. If it does, send the execution to a Wait node or end it. If it doesn’t, set the lock, run the workflow, then clear the lock at the end.
For production or higher concurrency, the better solution is an external queue. Push incoming requests into Redis, a database table, or a message queue, then have a separate worker workflow that processes one item at a time. This guarantees only one execution runs while others wait.
n8n doesn’t enforce execution level locking by itself, so anything “queue like” has to be implemented with state or an external system.
1 Like
I dont want it over-complicated, is there an easier solution? Also this is the same response chatgpt gave me
Just use a variable or flag to track if someone’s executing when a user starts, set it to “busy”, and when they finish, set it back to “available”. Other users just check this flag and wait/retry if it’s busy.
If you need something more robust, you could use a database with a simple lock table or Redis for distributed locking.
and I’ll the gpt comment as a compliment tho 
What workflow tool are you using? Might help me give you a more specific solution.
Cant you make it automatic why manually?
Oh yeah, totally You can automate it with a loop that checks the lock status automatically
something like
User hits the node
- Node checks if locked
- If locked, waits a few seconds and checks again (loop)
- If unlocked, locks it, executes, then unlocks