Automation

Everybody wants to automate, and almost nobody wants to build a graph. That is why this module is entered through the recipe catalogue, not through the editor.

The recipes

Eight ready-made automations, turned on in two or three clicks. They are the gestures you repeat: chase an overdue invoice, warn when stock drops below a threshold, create a follow-up when a quote is accepted, thank a new lead.

You turn them on, you set their two or three parameters, they run.

What triggers them

• A business fact — an invoice issued, a payment received, a deal won.
• A time — every Monday, the first of the month, in three days.
• An external call — a webhook, to connect a tool that is not here.

What runs

A sequence of steps: condition, loop, transformation, a call to a tool inside the software, a call to an external interface, or a pass through a language model when the text to produce cannot be templated.

Every run is recorded in the database , step by step, with its result. An automation that fails says so, and you see where.

The budget

This is the point that separates a promise from a tool.

• Every run consumes credits , according to the steps actually played.
• The monthly allowance is a hard ceiling : once reached, the run stops rather than keep charging.
• Overage is bought in steps, knowingly.

The editor

It exists, for sequences no recipe covers — a versioned node graph, with replay of a past run. It is reserved for organisations that ask for it, and it is not editable on a phone: a graph is not manipulated with a fingertip, and pretending otherwise would be a lie.