Copying a number from one system into another is not a job. It is a symptom of owning too many systems.
All of them cross application boundaries, because there are no application boundaries to cross.
Amount thresholds, role-based sign-off and multi-step chains on purchase orders, expenses, leave, discounts, credit notes and journal entries. The rule lives with the document, so it cannot be bypassed by using a different screen.
Purchase orders above 5,000 euro require the finance manager. Above 25,000, the director as well.
A document moves through defined states with rules about who can move it and what must be true first. Draft, submitted, approved, cancelled, with an audit trail that records who did what and when.
A leave request cannot reach approved while the balance is insufficient, whoever clicks the button.
When something happens in one application, something happens in another. No connector, no webhook, no third-party automation subscription, because both ends are the same system.
A won deal creates the sales order, reserves the stock and opens the onboarding project.
Recurring jobs that run whether or not anyone remembers them: recurring invoices, subscription renewals, depreciation, reorder checks, reminder emails, report delivery and data exports.
Overdue invoices are chased on day 7, 14 and 30 with escalating tone and a copy to the account owner.
Conditional alerts by email, in-app or chat, aimed at a role rather than a person, so that a departure or a holiday does not silently break the process.
Stock below reorder level notifies whoever holds the purchasing role today.
Where a rule is not enough because the work needs judgement or language. The agent drafts, summarises or proposes, and a person accepts. Automation for the deterministic part, an agent for the rest.
The Finance Agent drafts the dunning email in the customer's language, referencing the actual open items.
Most disappointment with automation comes from asking a rule to use judgement, or asking a person to behave like a rule.
Deterministic and auditable. If the condition is true, the action happens, every time, and you can prove it happened.
Handled by an agent that reads live data, proposes an action and waits for approval on anything with consequences.
Left with the decisions that should not be delegated, and none of the copying between systems that used to fill the day.
Approvals, notifications, assignment rules, workflows and scheduled reports are configured in the interface by an administrator. Nothing is deployed and nothing needs a developer.
Server-side scripts for the cases a form cannot express, with the same permission model and the same audit trail as everything else.
Every rule change is recorded with who changed it and when. A rule that turns out to be wrong is turned off, not archaeologically investigated.
Try a change on a staging Site made from a copy of your production data before it starts blocking real approvals on a Friday afternoon.
A customer orders online at 07:40. Stock is reserved, the sales order exists, and the accounting entry is already correct. At 08:00 the reorder check notices the item has dropped below its level and drafts a purchase order to the preferred supplier at the agreed price.
It is 6,200 euro, so it waits for the finance manager, who approves it from her phone before the office opens. The customer emails at 09:15 asking about delivery. The Support Agent drafts a reply containing the real shipment and the real date, an agent reads it, sends it, and moves on.
Nobody exported anything. Nobody asked the warehouse. Nobody opened a second system. That is the entire product argument in one morning.
For work inside the suite, no. The applications share a database, so a trigger in one is a direct write in another rather than a message that might arrive. External connections are handled separately, and those are documented on the integrations page.
An administrator in your company, usually with our help during onboarding. Most of it is a form. The point of configuring it yourself is that when the business changes on a Tuesday, the rule changes on a Tuesday.
Rules run with defined permissions and every action is logged against the rule that caused it. Anything financial passes the same validation a person would. And you can see, per document, exactly which rule fired.
Only where you have allowed it, and by default nowhere that has consequences. Agents draft and propose. Sending money, changing a price or altering a record requires a person, unless you deliberately loosen that for a low-risk task.
It uses compute like everything else, and compute is one of the three meters that decide your plan. Ordinary approvals, notifications and nightly jobs barely register. Very heavy agent activity or enormous scheduled reports are what eventually move a company up a plan, and we tell you before that happens rather than billing an overage.
