Removing the spreadsheet that held operations together.
The client had a weekly routine: export orders, reshape them in a spreadsheet, upload to the accounting system, message two colleagues about the exceptions. It worked until the person doing it took leave.
The problem
A process living in one person’s head.
The steps were undocumented because they had never been designed — they accumulated. Each one was individually reasonable and collectively fragile.
Exceptions were the real volume. Orders with mismatched SKUs, refunds that arrived after reconciliation, currency rounding that never quite agreed. All handled by judgement, none recorded.
A hosted automation tool had been tried and abandoned: it managed the straightforward cases and failed silently on everything else.
The hard parts
Exceptions are the job.
- The majority of operational effort sat in exceptions, not the happy path
- Finance data means an error is not just noise — it has to be caught before it is written
- Some steps genuinely need judgement and cannot be fully automated
- Silent failure was the previous tool’s fatal flaw and had to be designed out
- Workflows had to be reviewable, because operations staff would inherit them
Architecture
How a workflow runs.
- 01triggerA webhook, schedule or record change starts the run
- 02validateInput is checked against expected shape before anything downstream is touched
- 03transformData is reshaped once, in one place, replacing four spreadsheet steps
- 04assistWhere judgement is needed, a local model classifies and a human approves
- 05writeResults are written to Zoho or Xero and the write is confirmed
- 06reportSuccesses are logged; failures are surfaced with enough context to act on
- 07versionWorkflows are versioned so a change can be reviewed and reverted
Stack
- n8n
- Webhooks
- Shopify
- Zoho
- Xero
- Google Sheets
- Laravel
- Ollama
What shipped
What shipped.
- Self-hosted n8n with versioned, reviewable workflows
- Order flow from Shopify into the accounting system without manual reshaping
- Explicit exception handling with a human approval step where money moves
- AI-assisted classification for the steps that genuinely need judgement
- Google Sheets reporting for the teams that live in spreadsheets
- Failure reporting with context, replacing silent retries
Result
Weekly
Manual routine removed
The routine no longer depends on a person.
The weekly export-and-reshape routine is gone. Orders move from Shopify into accounting continuously, and exceptions are raised rather than absorbed.
Because failures surface with context, the operations team can act on them the same day instead of discovering the problem at month end.
Workflows accumulated after launch, which is the normal pattern once a team can see what is possible.
Related
Read next.
Next step