Automations

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

When this happens, do that — with a count, because an automation that has never run is broken or unnecessary.

The count is the diagnostic. Without it a dead rule is indistinguishable from a quiet one.

Triggers are conditions the system already knows about, not new instrumentation.

How it works

1
A rule is defined as when this happens, do that.
2
Triggers use conditions the system already knows about rather than new instrumentation.
3
The firing count is the diagnostic — without it a dead rule and a quiet one look the same.
4
A rule that has never fired is surfaced rather than left to accumulate.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Automationrequired	text	What it does, named as the outcome.
Whenrequired	text	The trigger condition, drawn from what another module already tracks.
Thenrequired	text	What should happen when the trigger fires, stated as the outcome wanted.
Firedrequired	text	How many times. An automation that has never run is broken or unnecessary.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Triggers are limited to what existing modules record.
No chaining; one automation cannot trigger another.
No dry-run or preview before enabling.
Failures inside an action are not retried.

Before it works

What you have to provide, if anything.

Needs the module holding the trigger condition to exist first.
Check the fired count after a fortnight. A zero means the trigger can never be true.

In practice

A business chasing invoices and stock by hand.

“Chase an invoice automatically once it is a week overdue.”

What was said to the agent

What the agent built

An automation with a trigger, an action and a firing count.

What changed

It fired eleven times in two months. The Friday handover rule fired zero — its trigger could never be true, and it was deleted.

Better with

These do a different job on the same data. An agent can have all of them.

RemindersLive

The failure mode is forgetting at the right time — renewals, follow-ups, anything with a date that arrives quietly.

WebhooksLive

Other systems notify this one, or it notifies them, and a missed event has real consequences.

InvoicesLive

The agent bills clients or is billed by suppliers, and someone needs to see what is unpaid without opening the accounting tool.

Questions

What data does the Automations page use?

It reads automation records the agent has collected. Triggered flows. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.