Automation library · Integrations

Redis locking for concurrent task handling

Started by another system calling it, and works across Redis. 14 steps, 4 branches, 1 loop or waits: a working afternoon to understand properly.

Medium

Download free
14 stepsMedium: a working afternoon
4Branches: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Logic 10Service 3

The steps in the order they run, from what starts it.

  1. 1Incoming Webhook DataWebhookStarts it
  2. 2Fetch Webhook Data & Declare lockValueCodeLogic
  3. 3Check Redis LockRedisService
  4. 4redisLock existence booleanIfLogic
  5. 5Acquire Redis LockRedisService
  6. 6redisLock acquired booleansIfLogic
  7. 7Workflow SwitchSwitchLogic
  8. 8Poll for lockWaitLogic
  9. 9Workflow 1SetLogic
  10. 10Workflow 2SetLogic
  11. 11Workflow 3SetLogic
  12. 12duplicateWebhook booleanIfLogic
  13. 13Discard Redis LockRedisService
  14. 14ENDNo OpLogic

How it's built

Starts on
Another system calling it
Steps
14, with 4 branches, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Redis
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Redis account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 14 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.