Automation library · Integrations

Building a consistent storytelling AI on autopilot with Redis

Started by another system calling it, and works across Redis. 11 steps: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 2Logic 4Service 5

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

  1. 1StartStartService
  2. 2Initialize MemorySetLogic
  3. 3Receive PromptWebhookStarts it
  4. 4MemoryRedisService
  5. 5Gemini Flash APIHttp RequestService
  6. 6Extract Story ElementsSetLogic
  7. 7Process Story OutputFunctionLogic
  8. 8Update MemoryFunctionLogic
  9. 9Fish Audio APIHttp RequestService
  10. 10Store MemoryRedisService
  11. 11Return Story SegmentRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
11
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. 11 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 11 steps before you point it at anything that matters.