n8n automation
Workflows you own, running where your data lives
We design and build n8n workflows in your own instance, on your server or in n8n Cloud. Every workflow comes with error handling, a log you can read and a written description of what it does.
n8n · new order
- ShopifyOrder placed
- n8nCheck and route
- ERPStock reserved
- GmailConfirmation sent
- In stockBook the pickup
- MissingTell purchasing
What it is
An automation tool you can host yourself
n8n is a workflow tool where each step is a node: a trigger, a call to another system, a condition, a piece of code. It can run on a server you control, which matters when the data should not pass through one more third party, and it does not limit you to the connectors someone else has built. We choose it when workflows are long, run often, or need logic that visual tools handle badly.
- Self-hosted or cloud: on your server, or in n8n Cloud under your account
- Any system with an API can be connected through the HTTP Request node
- Code nodes for the logic that does not fit a box-and-arrow diagram
- Workflows exported and versioned, so a change can be reviewed and undone
Executions · sample data
- Order to warehouseSucceeded · 6 nodesRunning
- Enquiry to CRMSucceeded · 4 nodesRunning
- Invoice to accountingWaiting for approvalRunning
- Daily stock syncRetried once, then succeededRunning
What we deliver
A running instance and workflows you can trust
Instance setup
n8n installed on your server or set up in n8n Cloud, with backups, updates and access for the right people.
Workflow build
Triggers, branches and data mapping built from the process we mapped with you, tested on real examples.
Error handling
Retries for temporary failures, an error workflow for the rest, and a message to a named person when something needs attention.
Credentials and access
Each connection uses its own credential with the narrowest permissions that work, stored in n8n and never in a workflow.
Approval steps
Where a mistake would be costly, the workflow stops and waits for a person to confirm in email or team chat.
Documentation
A page per workflow: what starts it, what it changes, what can go wrong and what to do then.
How a project runs
From one mapped process to a workflow in daily use
- 01
Map the process
We follow one real case from start to finish and write down every system, hand-off and exception.
- 02
Set up the instance
We agree where n8n runs, who has access and how it is backed up, before the first workflow is built.
- 03
Build and test
The workflow is built against test data, then run beside the manual process until the results match.
- 04
Hand over and watch
You get the documentation and a walkthrough. We watch the first weeks of executions and fix what real data reveals.
What n8n connects to
- n8n building blocks
- Webhook, Schedule trigger, HTTP Request, Code, IF and Switch, Error workflow
- Commonly connected
- Gmail and Outlook, Pipedrive, HubSpot, Odoo, Shopify, WooCommerce, Slack and Teams, Google Sheets
- Where it runs
- Your own server, A cloud server in the EU, n8n Cloud
We start from what you already have. The list shows what we reach for when something is missing, not tools you must adopt.
Is n8n the right tool?
A good fit when…
- Workflows run many times a day and usage-based billing would add up
- Data should stay on infrastructure you control
- A system you use has an API but no ready-made connector
- The logic has branches, loops and exceptions
Probably not for you when…
- You need two or three simple automations and nobody to look after a server
- The team wants to edit workflows themselves with no technical help
- The systems involved have no API and no export
- The process itself is still changing every week
Use cases
What we build in n8n
Each of these is a workflow, or a small set of them.
Every enquiry in the CRM, without retyping
Enquiries from forms, email and chat become contacts and deals in your CRM, with the right person notified.
Open use case SalesBusiness automationCRM implementationQuotes drafted from your price list
A quote is drafted from the deal, your price list and current stock, and waits for a salesperson to approve it.
Open use case SalesCRM implementationBusiness automationNo open quote left without a follow-up
The CRM reminds the owner, drafts the follow-up and shows which deals have gone quiet.
Open use case SalesCRM implementationBusiness automationA sales report nobody has to build
Pipeline, won and lost deals and activity, delivered on a schedule straight from the CRM.
Open use case Finance and adminAI integrationsBusiness automationSupplier invoices read, matched and ready to post
Incoming invoices are read, matched to purchase orders and sent for approval before they reach the books.
Open use case Finance and adminAI integrationsBusiness automationData out of documents, into your systems
Contracts, forms, delivery notes and statements are read and their data placed where it is needed.
Open use case Finance and adminBusiness automationERP and business systemsOverdue invoices chased politely and on time
Reminders go out on a schedule from your open invoices, and the awkward cases go to a person.
Open use case Finance and adminBusiness automationAI integrationsThe monthly report, assembled for you
Figures from accounting, sales and operations pulled into one report on a schedule, with a written summary.
Open use case Customer supportAI integrationsBusiness automationA support inbox that sorts itself
Incoming messages are sorted by topic and urgency, routed to the right person and given a draft reply.
Open use case Customer supportBusiness automationAI integrationsCustomers check their order without writing to you
Order and delivery status available on your site or by reply, pulled live from the shop and the courier.
Open use case OperationsBusiness automationERP and business systemsOrders that reach the warehouse on their own
An order placed in the shop or by email appears in the ERP, on the pick list and with the courier, entered once.
Open use case OperationsERP and business systemsBusiness automationOne stock figure in every system
Stock levels kept in step between the warehouse, the ERP and every sales channel.
Open use case OperationsBusiness automationCustom softwareNew colleagues ready on day one
Accounts, equipment, documents and first-week tasks set in motion from one form.
Open use caseQuestions about n8n
n8n or Make: which should we use?
Make is quicker to start with and needs no server, which suits a handful of straightforward scenarios. n8n suits workflows that run often, need custom logic or should run on your own infrastructure. We work with both and recommend one after we have seen the process, with the reasons written down.
Should we self-host or use n8n Cloud?
Self-hosting gives you control over where data is processed and no limit set by a plan, but someone has to keep the server updated and backed up. n8n Cloud removes that work. We set up either, and we can look after a self-hosted instance under a care agreement.
Who owns the instance and the workflows?
You do. The server or cloud account is in your name, the workflows are yours to export, and the documentation is written so another developer could take over.
What happens when a workflow fails?
Temporary failures are retried. Anything else goes to an error workflow that records what happened and tells a named person, with enough detail to act on. Nothing fails silently.
Can our own people change the workflows later?
Yes. We build them to be readable, name the nodes for what they do and walk your team through them. Small changes are usually within reach of a technically minded person.
Can n8n use AI models?
Yes. A workflow can send text or a document to a model, get structured data back and continue. We add a check by a person wherever the result would be costly to get wrong.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples