No monthly run cap
Automations fire as a side-effect of the work — there's no per-tier "automated actions per month" meter to ration. Build the workflows your process needs without watching a usage counter.
Triggers that match real events
Fire when a row changes, when a new row is added, or on a date schedule. Row-change triggers can fire on an exact value, on becoming a value (a true transition), or on any change at all — so a status going to "Done" runs once, not every time the row is saved.
A real action catalog
Notify someone (a fixed address or a contact column, with templated subject/body), set a cell, set a date, assign a person, clear a cell, or move and copy a row to another sheet — the classic "archive completed rows" workflow, built in.
Multi-step approvals that actually pause
Drop a Request-approval step into a rule and it suspends mid-run. The approver gets an email with a clean decision page — rule, sheet, a safe summary of the row, approve or reject. On approval the automation resumes at the exact next step; on rejection it can run a different branch. It's a real stateful gate, not a notification.
Conditions with AND / OR
Gate a rule on several conditions joined with AND or OR. Combine "Priority is High" with "Owner is empty" to route only the rows that matter.
A complete run history
Every rule keeps a history of what fired, on which row, and how it ended — sent, skipped, or errored — viewable per rule or across the whole sheet. When someone asks "did the reminder go out?", you have the receipt.
Safe by construction
Each rule runs in its own scope, so one bad action can't starve the rest, and automation-driven writes don't re-trigger automations — no runaway loops. Actions check the rule author's access at run time, so a workflow can't reach a sheet its owner can't.