Automations

Trigger → conditions → actions: a task, a notification, an email, an approval, a field or a webhook. Automations create work for people; they never move money.

Settings → Automations. Three tabs: Automations, Tasks, Run log.

Triggers are events in the books — an invoice created, paid or overdue; a bill arriving or due soon; an expense recorded; a project margin dropping or budget passing a percentage; a customer balance going past due; bank lines piling up unreviewed. Conditions narrow them: greater than, less than, exactly, contains, on any field of the record (amounts are in cents — $10,000 is 1000000). Actions: create a task (title with merge fields like {number}, {customer_name}, {balance_cents}; due in n days; assigned to someone), send an in-app notification or an email, require approval, set a field, or call a webhook.

The boundary. An automation may create work for a person, ask for an approval or set a field. It cannot post, pay, send an invoice or apply a payment. Money moves only when a person acts — that is a rule of the product, not a missing feature.

Starter templates cover the usual cases — chase an invoice at 7 days overdue, flag a bill over a threshold for approval, warn when a project passes 80% of budget. The run log records every firing with its outcome and context, and replay runs a logged firing against today's data to see what it would do now. Tasks created by automations, the close checklist and the books review all land on the Tasks tab.