Hire a freelance n8n developer when you have one or a few well-defined workflows to build. Bring in an n8n consultant when you first need someone to decide what to automate and how: architecture, hosting, security and priorities. Choose an n8n agency when the workflows touch your CRM, your customers and several systems at once, and you need them monitored, maintained and covered when someone is on holiday. Many companies end up with a mix: a consultant or agency for the design, then a freelancer or an in-house person for small changes.
This guide covers what each option delivers, the skills to vet, the questions to ask, the red flags, and how to contract and hand over n8n work.
What’s the difference between an n8n freelancer, consultant and agency?
| Freelance n8n developer | n8n consultant | n8n agency | |
|---|---|---|---|
| What you get | Hands-on builds of specific workflows | Process review, automation roadmap, architecture and guidance; sometimes the build | Discovery, build, hosting, monitoring and ongoing changes from a team |
| Best for | One clear workflow or integration, small changes | Deciding what to automate, setting standards, unblocking an in-house team | Several connected workflows, CRM and customer-facing automation, AI steps that need review |
| Typical pricing | Hourly or fixed price per workflow | Hourly, day rate or fixed-price audit | Fixed-scope builds plus a monthly retainer |
| Your effort | You manage scope, testing and handover | You or your team implement the plan | Lowest day to day, but you still own decisions and approvals |
| Main risk | Single point of failure; weak documentation | Advice without implementation | Higher cost; workflows hosted in their account if you’re not careful |
When is a freelance n8n developer the right choice?
A freelancer is a good fit when the job is clear and contained:
- Sending new leads from Typeform or a website form into HubSpot or Zoho, with a Slack alert to sales.
- Syncing customers or orders between Shopify and your email or accounting tool.
- A weekly report pulled from a few sources into Google Sheets or Slack.
- Connecting one niche API or webhook that no ready-made integration covers.
- Fixing or extending a workflow someone else built.
You get direct access to the person doing the work, quick turnaround and lower overhead. What you take on is project management, testing and making sure the knowledge doesn’t leave with them.
When do you need an n8n consultant?
Consulting is the “what and how” before the “build”. A good n8n consultant maps your processes, finds the two or three automations that pay back first, and decides how they should be built: self-hosted or n8n Cloud, how credentials are stored, how errors are handled, how workflows are versioned, and where a person must approve AI output.
Development without that step works for single workflows. Once you have ten workflows touching the same CRM, missing design decisions show up as duplicate records, silent failures and nobody knowing which workflow does what. Hire a consultant when you have an in-house person who can build but needs direction, or when you want an independent review of what already exists.
When is an n8n agency worth it?
An agency makes sense when automation becomes part of how the business runs:
- Workflows write to your CRM, email customers or touch billing.
- Several systems are connected, so a change in one breaks another.
- AI steps are involved and need a review process.
- You need monitoring, fixes and changes every month, with cover for holidays and sick days.
- The automation sits next to ads, analytics or CRM work that the same team runs.
Goodish is one of these agencies, so weigh this accordingly. We’re a senior team in Slovenia working mostly with US companies. We build in n8n, with OpenAI, Claude or Gemini where AI is needed, and every AI step writes to a review queue that only a person empties. For iSoftpull we run the CRM end to end and act as their API integration partner: client web forms go straight into the iSoftpull API and data stays in sync with the CRM (the iSoftpull case). We quote on scope after a free audit; see our AI and automation service. If you want to compare agencies, see our list of n8n agencies and how to choose one.
What skills should an n8n developer have?
Core n8n
- Nodes, expressions and data mapping between items.
- The Code node (JavaScript or Python) for logic no node covers.
- Sub-workflows for reuse, and error workflows that alert someone when a run fails.
- AI nodes (AI Agent, LLM chains, vector stores) if your project uses them, plus a review step before output goes anywhere important.
APIs and data
- REST and GraphQL, webhooks in and out.
- Authentication: OAuth2, API keys, token refresh.
- Pagination, rate limits and retries with backoff.
- Data cleaning, deduplication and idempotency, so a retried run doesn’t create duplicates.
Running n8n
- Docker, environment variables, Postgres, and queue mode for higher volume on self-hosted instances.
- Credential handling, user management and updates.
- Version control for workflows, exported to Git or through n8n’s source control features where your plan includes them. See managing n8n at scale with Git and CI/CD.
Match seniority to the job
| Level | Can handle | Fits |
|---|---|---|
| Junior | Simple workflows from a clear spec, with review | Notifications, two-app data transfers |
| Mid-level | Independent builds, moderate troubleshooting, most integrations | Typical CRM, form and reporting workflows |
| Senior | System design, complex API orchestration, custom nodes, performance and security | Multi-system automation, AI agents, self-hosted infrastructure |
How do you vet an n8n developer or consultant?
- Look at real workflows. Ask for an exported workflow (with credentials removed) or a screen-share of one in production. Check for descriptive node names, notes, sub-workflows and an error path.
- Ask about failure. “Tell me about a workflow that broke in production. How did you find out, and what did you change?” Good answers mention alerts, logs and retries.
- Give a small paid test. A two-to-four-hour task close to your real problem tells you more than any interview.
- Ask about your process first. Strong candidates ask why a step exists before they discuss how to automate it.
- Check references from clients whose workflows have been running for months, not just launched.
Questions worth asking:
- How do you store and share credentials?
- How would you stop a retried run from creating duplicate records?
- Self-hosted or n8n Cloud for us, and why?
- How do you keep personal data out of AI prompts?
- What will you hand over at the end, and could another developer take over from it?
n8n offers official courses, but there is no widely recognised certification, so judge by shipped work and community activity (answers on the n8n community forum, published templates or nodes).
What are the red flags?
- Very low prices paired with very short timelines.
- No questions about your business, only about which apps to connect.
- No mention of error handling, monitoring or what happens when an API changes.
- Workflows built in the developer’s own account, with your credentials, and no export plan.
- Vague portfolio descriptions and no references.
- AI steps that send emails or edit records with no human check.
How should you price and contract n8n work?
Three models are common: hourly (good for small changes and maintenance), fixed price per workflow or project (good for well-defined builds) and a monthly retainer (good for ongoing changes and monitoring). Rates vary widely with experience, region and complexity, so compare scopes, not hourly numbers.
Whichever you choose, put these in writing:
- Statement of work: each workflow, its trigger, its systems and what “done” means.
- Ownership: you own the workflows, code and documentation.
- Accounts: workflows run in your n8n instance or your n8n Cloud account, with credentials you control.
- Confidentiality: an NDA before sharing data or processes.
- Milestones: payment tied to tested, accepted workflows.
- Support: who fixes what after launch, how fast, and how it’s billed.
How do you run an n8n project and hand it over?
- Discovery: map the current process, its volume and its exceptions.
- Design: agree the workflow structure, error handling and approval points before building.
- Build and test: test on real data in a copy or sandbox, including the edge cases.
- User acceptance: the people who own the process sign off.
- Launch and monitor: an error workflow posts failures to a channel with a named owner.
- Handover: documentation covering what each workflow does, its trigger, the credentials it uses, custom expressions and code, known limits, and how to pause it.
Good documentation is what lets you switch developers later without starting over.
Should you self-host n8n or use n8n Cloud?
n8n Cloud is the simplest: n8n runs the infrastructure and updates. Self-hosting gives you full control over where data lives and can be cheaper at volume, but someone has to run the server, back it up and keep it secure. Our n8n hosting guide compares the options.
FAQ
How much does it cost to hire an n8n developer?
It depends on scope and seniority. Freelancers usually charge by the hour or a fixed price per workflow; agencies quote fixed-scope builds plus a retainer. At Goodish, we quote on scope after a free audit; the price depends mostly on the number of systems involved. Hosting and any AI model usage are running costs on top.
Where can I find n8n freelancers?
The n8n community forum, freelance marketplaces and referrals from other n8n users are the usual places. Whoever you find, vet them on real workflows and a small paid test.
What does an n8n consultant do that a developer doesn’t?
A consultant decides what should be automated and how: priorities, architecture, hosting, security and standards. A developer builds the workflows. Many people do both; the question is whether your project needs the design work before the build.
Can an n8n developer migrate our Zapier or Make automations?
Yes, and it’s a common first project. Workflows are rebuilt rather than imported, which is a good moment to remove automations nobody uses. See migrating from Make to n8n.
Not sure which kind of help you need? Tell us about the workflows and we’ll say honestly whether a freelancer would do.
