n8n Automation Agency: What We Build and How It Works

What n8n is, in plain terms

n8n is a workflow tool. You connect the apps your business already uses, such as your forms, inbox, CRM, accounting tool and spreadsheets, and tell it what to do when something happens. A new form entry arrives, so it adds the lead to the CRM and sends a reply. An invoice lands in an inbox, so it reads the details and records them.

You build these workflows in a visual editor by placing steps on a canvas and joining them up. When the built-in steps are not enough, you can add a code step to reshape data or handle a case the standard steps do not cover. That mix of visual steps and code is the main reason technical teams like it.

n8n can be used two ways. You can use it as a hosted service, where n8n runs it for you, or you can self-host it on your own server. The workflows look the same either way. What changes is who looks after the server and where your data sits.

When n8n automation is the right pick, and when it is not

n8n is a good tool, but it is not the right answer for every job. A good agency will tell you when something else fits better. We cover the full comparison in moonlab.space/guides/zapier-vs-make-vs-n8n. The short version is below.

• Choose n8n when you want the workflows and their data on your own server, when the logic branches or needs small pieces of code, or when you expect to add AI steps and want control over how they run.
• Choose Zapier when the workflow is short and linear, uses popular apps, and will be looked after by someone on your team who is not technical.
• Choose Make when you want a hosted visual canvas for workflows with several branches or a lot of data reshaping, and you do not need to self-host.
• Choose custom code when the process is central to the business, runs at high volume, handles very sensitive data, or needs a system that no workflow tool connects to well.

What an n8n automation agency typically builds

Most n8n workflow automation projects fall into a few familiar types. The examples below are hypothetical, to show the shape of the work rather than a real client.

• Lead capture and instant reply. A cleaning company gets leads from its website form and two directories. The workflow collects each lead in one place, adds it to the CRM, sends the customer a reply within a minute and alerts the owner on their phone.
• CRM sync. A small agency keeps clients in one CRM and projects in a separate tool. When a deal is marked won, the workflow creates the project, copies the contact details and keeps both records matched when either one changes.
• Invoice and document processing with an AI step. A wholesaler receives supplier invoices as PDFs by email. The workflow pulls each attachment, uses an AI step to read the supplier, date, amount and line items, checks them against simple rules and adds them to the accounting tool. Anything that fails a check goes to a person for review.
• Support email triage. An online shop gets a mix of order questions, returns and complaints in one inbox. An AI step sorts each email by type and urgency, adds a label, drafts a reply for common questions and sends urgent ones to the right person straight away.
• Weekly reports. A service business wants Monday numbers without someone building a spreadsheet by hand. The workflow pulls bookings, revenue and open tickets from three tools every Monday morning and sends a short summary to the owner by email.

n8n AI automation: where the AI step helps

Two of the examples above use AI, and that is where n8n AI automation is most useful: reading free text that a fixed rule cannot handle, such as an email, a PDF or a customer message. The AI step turns that text into structured data or a draft, and the rest of the workflow follows normal rules.

AI steps need more care than rule-based ones. They can give a wrong answer with full confidence, they add a usage fee from the AI provider, and they need testing on real examples before they touch customers. A sound design checks the AI output against simple rules and sends anything unclear to a person. If a fixed rule can do the job, use the rule.

Self-hosted vs hosted n8n

This choice matters more with n8n than with most tools, because self-hosting is a real option. Neither choice is right for everyone.

• Data control. Self-hosting keeps workflow data on a server you control, which helps when you handle personal, health or financial records. With the hosted service, your data passes through n8n's infrastructure, so read their terms on where it is stored and processed.
• Maintenance. A self-hosted server needs backups, monitoring, disk space checks and a plan for when it goes down. The hosted service handles that for you.
• Who patches it. n8n releases updates, some of them security fixes. On the hosted service n8n applies them. On your own server someone has to apply them, test that your workflows still run afterwards and roll back if they do not. Agree in writing who that person is.
• Cost. Hosted pricing and self-hosting costs are structured differently. For self-hosting, count the server and the time to look after it, not only the licence. Check n8n's site for current terms.

What to expect from an n8n automation agency

Building a workflow that runs once in a demo is the easy part. What you are paying an agency for is a workflow that keeps running, tells someone when it fails, and that you can still own if the agency is gone. Expect these as standard.

• Scoping first. A written description of each workflow, what starts it, what it does, what it should do with unusual cases and how you will know it works, agreed before building starts.
• Built in your own accounts. The n8n instance, the app connections and the API keys belong to your business, not to the agency or to one employee's personal login.
• Error alerts. When a run fails, a named person gets a message with enough detail to act on it. A check that the workflow is still running at all, because a stopped workflow sends no errors.
• Documentation. A short plain-language note per workflow covering its purpose, trigger, connected accounts, known limits and owner.
• Handover. A walkthrough with your team, access to everything, and a clear answer on what support looks like after delivery and what changes cost.

Questions to ask before you hire an n8n expert

Whether you hire an n8n expert as a freelancer or an agency, these questions sort careful builders from the rest. Good answers are specific. Vague answers are a warning.

• Would you use n8n for this, or is another tool or custom code a better fit? Why?
• Should we self-host or use the hosted service, and who will update and back up the server if we self-host?
• Whose accounts will everything run in, and what do we keep if we stop working together?
• How will we find out when a workflow fails, and how quickly will you respond?
• What happens to a case the workflow cannot handle?
• How will you test it before it touches real customers or real data?
• Is the price fixed, what does it include, and which tool or AI usage fees will we pay on top?

How Moonlab works

Moonlab builds automations in n8n, Make, Zapier and custom code. Every project starts with a free 30-minute audit. We look at the task, tell you whether it is worth automating and which tool we would use, and agree a fixed price before any work starts. A single automation starts from $99 as a one-time project, and there are monthly plans at $199 and $399 per month for ongoing work and monitoring.

We do not start from n8n and look for a use for it. Our rule is this: "We pick the simplest tool that will still be reliable in a year. That means no-code where it fits and custom code where it doesn't." If n8n is the right tool, we build it in your accounts with alerts and documentation and hand it over. If something simpler will do, we will say so.

Book an audit at moonlab.space/contact. Related services: operations automation at moonlab.space/services/operations, custom builds at moonlab.space/services/custom-build, and web apps and SaaS at moonlab.space/services/web-apps-and-saas.