n8n automation, run like software

Who this is for

Two kinds of businesses. The first already runs automation, and all of it lives in one person's browser tab. The workflows were built in the editor, changed in the editor, and exist nowhere else. Nobody can say with confidence what is running, what was switched off on purpose, or what last Tuesday's edit actually changed. If that person leaves, or their account is compromised, or a well-meaning edit breaks the workflow that moves money, there is no record to consult and no version to roll back to.

The second has no automation yet, just the manual work: leads re-keyed from forms into the CRM, emails copied between systems, the same lookup performed forty times a week. They want automation built from the start the way it should be, rather than accumulating the first kind of problem.

What we deliver

An n8n instance on infrastructure you own: your server, your database, your backups. n8n is the open-source workflow platform we standardize on, and like every system we build, it belongs to the client at the end of the engagement, not to us and not to a vendor.

Every workflow lives as JSON in a repository and deploys one-way through CI: the repository is the source of truth, and what runs in production is what the repository says runs. Changes get reviewed before they touch production, because a workflow that writes to the CRM or emails customers deserves at least the scrutiny a CSS change gets on the website. Review is where the embarrassing failures get caught before customers find them: the test filter left in, the credential pointed at the wrong account.

Three disciplines round it out. Workflows are committed inactive, and activation state is managed deliberately, so a deliberate switch-off is a recorded decision that a routine redeploy cannot silently reverse. Changes land in a staging instance against test data before they promote to production. And credentials never go in the repository: n8n holds the secrets, the workflow JSON references them by name, and the repository stays safe to share with a reviewer, a contractor, or a successor.

What we automate

The work that sits between systems: lead intake from forms and channels into the CRM, email sync and drafting, prospect enrichment, deduplication, internal notifications when something needs a human, and the quote-to-cash steps where a deal moves from agreed to invoiced. The pattern is consistent: anywhere a person is re-keying data or babysitting a handoff between two tools, a workflow can hold that job permanently and never skip a step.

Proof

Sprout IQ, our own publishing business, runs 117 n8n workflows in production under exactly this discipline as of June 2026 (lead intake, email sync and drafting, enrichment, deduplication, and the pipeline that feeds the magazine content process), every one of them deployed from version control through CI. The full approach, including what the setup actually costs in time and when it is not worth it, is documented in Version Control for n8n: Running 100+ Production Workflows from a Repository.

Questions we get asked