The three components
A trigger is a specific state change: a status becomes Won, a timer exceeds four hours, a record is created. A condition narrows when the rule applies: only for expenses above a threshold, only for one branch. An action is what happens: create a record, notify a person, reassign an owner, raise a priority.
Automation versus integration
An integration moves data between two systems that each hold their own version of the truth, which means field mapping, a sync window and something that breaks whenever either side changes. Cross-module automation on a shared data core is not synchronising two records: it is acting on one, so there is nothing to map and nothing to drift.
Common cross-module automations
- Won deal to invoice: removes the sales-to-finance handoff and the day of billing latency it costs
- New hire to payroll setup, a new joiner is payroll-ready on day one
- Attendance to payroll, late marks and absences flow into the run with no monthly file upload
- SLA breach to escalation. See SLA
- Multi-level approval routing. Expenses above a threshold require two approvers
- Lead reassignment on rep inactivity. The pipeline keeps moving through absence
How to prioritise
Map every place work crosses a departmental boundary and ask what breaks when the responsible person forgets. Rank by that answer. In most businesses the top three touch money and customers: won-deal-to-invoice, new-hire-to-payroll and SLA escalation.