Process automation suite · 2025
n8n workflows for operations
Shipped
- Role
- Independent engineer
- Stack
- n8n, REST APIs, Webhooks
- Status
- Shipped
Problem
Leads and invoices were typed into the CRM, then again into email tools, then again into accounting. The failure was not a missing SaaS seat. It was three systems that only met in a person's head.
Constraint
The client's CRM, mail, and ledger already existed. The work was to connect them, not to replace them with a fourth platform. A failed run has to be visible. A silent skip is worse than a loud error.
Architecture
- CRM
- n8n
- Accounting
- Error path
- Run log
Decisions
n8n as the bus
Fifteen workflows, not a custom daemon, because the operators already needed a canvas they could pause. The value is the paths and the error handling, not the brand of the runtime.
Webhooks and REST as they actually are
Each system kept its own API. The suite does not invent a universal schema. It maps the fields that move and leaves the rest alone.
Error path on every flow
A dead credential or a 422 does not strand the record. It lands in a log with enough context to retry.
No hero dashboard
The client did not need a new UI. They needed a lead that still arrived in the ledger when nobody had the tab open.
This is the kind of work that does not photograph well and does close. If your operations still depend on someone copying a row, the first message should name the three systems and the record that gets lost.
Outcome
Shipped. Manual re-entry is no longer the path between those three systems. Client name stays off this page.
What was handed over
- Workflow exports
- Credential map (names and locations, not the secrets)
- What each flow does, and which one to pause first
- Where the error log lives and how to retry a dead item