Automation library · Integrations

Create a simple data caching system

Started by a clock, and works across n8n data table. 13 steps, 3 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 8Service 3

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

  1. 1When Executed by Another WorkflowExecute Workflow triggerStarts it
  2. 21 Hour Clean for Cache TableSchedule triggerStarts it
  3. 3Check Action TypeIfLogic
  4. 4Drop all rows with expired cache entiresData TableService
  5. 5Action Write ValueNo OpLogic
  6. 6Read ActionNo OpLogic
  7. 7Upsert row(s)Data TableService
  8. 8Get row(s)Data TableService
  9. 9Return ValueSetLogic
  10. 10If not in CacheIfLogic
  11. 11No cache found, use error detection to detect this.Stop And ErrorLogic
  12. 12If Expired CacheIfLogic
  13. 13Return Value from CacheSetLogic

How it's built

Starts on
A clock
Steps
13, with 3 branches
Size
Medium: a working afternoon
Connects to
n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on a clock.

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