Automation library · Research and reporting

Summarize Umami data with OpenRouter

Started by a clock, and works across Baserow. 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 3Service 6

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

  1. 1When clicking ‘Test workflow’Manual triggerStarts it
  2. 2Schedule TriggerSchedule triggerStarts it
  3. 3Get view stats from UmamiHttp RequestService
  4. 4Parse Umami dataCodeLogic
  5. 5Send data to A.I.Http RequestService
  6. 6Get page data from UmamiHttp RequestService
  7. 7Parse Umami data1CodeLogic
  8. 8Get page view data from UmamiHttp RequestService
  9. 9Parse UmamiCodeLogic
  10. 10Send data to A.I.1Http RequestService
  11. 11Save data to BaserowBaserowService

How it's built

Starts on
A clock
Steps
11
Size
Medium: a working afternoon
Connects to
Baserow
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Baserow 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. 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.