LumenFlowAutomations that repeat

Say what should be true every Monday.

Describe the recurring job in a sentence. LumenFlow builds the steps, runs them on a clock or when a file lands, and leaves a formatted report — with the results already in LumenSheets — before you open your laptop.

Download freeSee a run

LumenFlow comes with Pro and up. Watching costs nothing; credits are spent only when a run starts.

Starts on
A clock or a fileHourly, daily, weekly or monthly
Runs
In the backgroundKeep working in any editor
Leaves
A formatted reportAnd the results in LumenSheets
When it fails
It stops and says whereNever a half-finished report

01What it does

Build it once, then stop doing it.

The same transformation, the same report, every week — handed to something that does not forget and does not need you there.

01Readable steps

Each step’s output is the next step’s input.

An automation reads top to bottom like the process it replaces: ingest, normalise, flag, report, pipe. Open any step and see exactly what it did to the data. Save it once and run it again on new inputs.

  • Reads like the process it replaces
  • Open and edit any step
  • Save once, re-run on new inputs
01Ingest
supplier-A.csvsupplier-B.xlsxsupplier-C.csvsupplier-D.csv
02Normalise
datesupplieramount2026-09-21Acme4,1202026-09-22Brook9802026-09-22Cole2,310
03Flag
suppliervs planAcme+2.1%Brook+7.4%Cole−6.2%
04Report
Weekly supplier summary
05Pipe
Supplier results · 12 rows flagged
You do not wire nodes together. You say what should be true, and it builds the steps that make it true — each one open to read and edit.

02The same transformation, a hundred times

Run one step across hundreds of rows or files. It works in the background, so a long job never blocks the editor you are in.

Every run ends in formatted output

84 of 112 supplier files normalisedIn the background · 1m 12s
Keep working in another editor — a long job never blocks the one you are in.

03A clock, or an event

Some work is weekly; some starts when something arrives. Either way the automation is already watching — and watching is free.

A clockHourly, daily, weekly or monthly MonTueWedThuFriSatSun07:00
Or an eventWhen a file lands in a folder /Exportssupplier-E.csvRun started
Watching costs nothing. Credits are spent only when a run starts.

04Honest failure

A run that cannot finish stops at the step that failed and names the reason. Fix it, retry that step, and it carries on.

Run · week of 31 AugStopped
Ingest4 files
Normalise“Invoice date” is missing in supplier-D.csv
MergeNot started
ReportNot started
Retry the stepNo half-finished report was sent.

05What Monday morning looks like now

The same two hours, every week — or thirty-eight seconds on Saturday night, with nobody there.

What you start with Four supplier files land every FridayDifferent column orders and date formatsTwo hours of copy-paste before anyone can lookA report rebuilt by hand every Monday
What you hand over One automation, scheduled for Saturday nightAll four files ingested and normalisedA formatted report on every runResults in LumenSheets when you open your laptop
2 hoursevery Monday, by hand38 secondsunattended, Saturday night · same four files

02LumenAgent automations

Ask once. Then stop asking.

LumenFlow runs pipelines over files and data. LumenAgent can keep any run worth repeating as an automation of its own — on a schedule, when a file lands, when a client writes in, or fifteen minutes before a meeting. Both watch for free.

Watches
Clocks, folders, inboxes and calendars
Spends
Only when a trigger starts a run
Replays
Free rows: a compiled recipe, no model call
Caps
What one run may spend — then it stops and reports

03The full toolkit

Everything LumenFlow does, start to finish.

Triggers, steps, runs and cost — all in one place you can read.

Triggers

When it starts.

  • On a schedule, hourly to monthly
  • When a file lands in a folder
  • By hand, on new inputs, any time

Steps

What it does.

  • Ingest files and exports
  • Normalise, merge, flag exceptions
  • Generate a formatted report
  • Pipe results into LumenSheets

Runs

How it behaves.

  • In the background, never blocking
  • History with time and files
  • Stops at the failing step, named
  • Retry just that step

Cost

What it spends.

  • Watching is free
  • Credits only when a run starts
  • Comes with Pro and up
  • Every editor stays free

04Works with the rest

The work that used to wait for Monday.

  1. Starts here

    A folder

    Supplier exports land on Friday, in four different shapes.

  2. Runs it

    LumenFlow

    Normalises, merges and flags exceptions on Saturday night.

  3. Writes it

    LumenDocs

    A formatted weekly summary, generated on every run.

  4. Lands in

    LumenSheets

    The results, ready to chart and share on Monday.

05Questions

Common questions

How is LumenFlow different from LumenAgent?

LumenAgent does a job with you, in conversation. LumenFlow runs a readable pipeline — the same steps over files and data — on a clock or when a file lands, with nobody there.

What can an automation do?

Chain steps that ingest files, transform them — normalise, merge, flag exceptions — and produce a formatted report, with results piped into LumenSheets.

What starts a run?

A schedule — hourly, daily, weekly or monthly — or a file landing in a folder. You can also run a saved automation by hand on new inputs at any time.

What does it cost?

Watching is free; credits are spent only when a run starts. LumenFlow comes with Pro and up, and every editor stays free.

What happens when a run fails?

It stops at the failing step and names the reason. Nothing half-finished is sent; fix the input and retry that step.

Stop doing it by hand.

Write down what should be true every week. LumenFlow keeps it true.

Download freeSee pricing

LumenFlow comes with Pro and up. Every editor is free.