Automation library · Integrations

Batch process data with Redis

Started by an event in a connected app, and works across Redis. 15 steps, 2 branches, 2 loops or waits: a working afternoon to understand properly.

Medium

Download free
15 stepsMedium: a working afternoon
2Branches: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 1Logic 5Service 9

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

  1. 1TriggerExecute Workflow triggerStarts it
  2. 2Get lock valueRedisService
  3. 3Is lock active?IfLogic
  4. 4Wait for lock releaseWaitLogic
  5. 5Push to message listRedisService
  6. 6CryptoCryptoService
  7. 7Set last update uuidRedisService
  8. 8WaitWaitLogic
  9. 9Get last update uuidRedisService
  10. 10Am I last?IfLogic
  11. 11Set lockRedisService
  12. 12Get messagesRedisService
  13. 13Clear messagesRedisService
  14. 14Release lockRedisService
  15. 15Split messagesSplit OutLogic

How it's built

Starts on
An event in a connected app
Steps
15, with 2 branches, 2 loops 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 an event in a connected app.

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. 15 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 15 steps before you point it at anything that matters.