How to Hire an n8n Developer: Questions to Ask First

To hire an n8n developer well, ask for one real workflow they built, ask what broke in it, and agree in writing who owns the instance, the credentials and the error alerts once it is live. Most bad hires fail on those three points, not on whether the person can drag nodes around a canvas.

We build n8n workflows for clients, so we have been on both sides of this conversation. Below is how we would hire for it: which kind of person fits which job, what to ask, what to put in the scope, and the red flags we have seen. If you would rather skip the search, our n8n consulting and build work is the short version.

Freelancer, n8n consultant or n8n agency

The three labels overlap, and the title matters less than the shape of the job. This is how we would split it.

Our own bias: we are an agency, so we would say that. The honest counterpoint is that for a single lead-routing flow, a good freelancer is cheaper and perfectly fine. We would only push you toward an agency when the work touches a CRM, a phone system and billing at once, because that is where nobody owns the failures.

What to ask before you hire an n8n expert

Skip the question about years of experience. n8n changes quickly and the skill that matters is how someone handles a run that goes wrong. These are the questions we would ask, and the answers we would want.

1. Walk us through a workflow you built. You want node names, the trigger, and what the data looks like at each step. Vague descriptions of "connecting your apps" are a warning.
2. What broke, and how did you find out? A real answer mentions an error workflow or alert that reached a person, not a customer complaint.
3. How do you test before going live? Look for pinned sample data, a test webhook, and a side-by-side run against real records when replacing an existing process.
4. Where do the credentials live? They should sit in n8n credentials under an account you own or control, not in the builder's personal workspace.
5. What happens when a node does not exist for our tool? A strong builder reaches for the HTTP Request node or a Code node and explains the API call. A weak one says it cannot be done.

We would also ask to see something running. Our Stripe deposit to project kickoff automation is a recorded run of one of our builds, step by step, including which steps ran and which were substituted. Whoever you hire should be able to show you something at that level of detail, even if it is with client details removed.

What to put in the scope

Most disputes we have heard about trace back to a scope that described the happy path only. Before anyone builds, write down these items.

• The trigger, and exactly what should happen for each outcome.
• What counts as a failure, and who gets the alert when a run fails.
• Who owns the n8n instance, the server if you self-host, and every credential.
• A handover: a short written description of each workflow and a walkthrough call.
• A support window after launch, with a stated length.

The failure item is the one people skip. A workflow that fails silently is worse than no workflow, because the team assumes the work is being done. We never hand over a build without an error path that reaches a human.

Hosting and cost, as of October 27, 2026

This is the section that goes stale. We read it off n8n.io/pricing today. The page lists Cloud Starter at 20 euros a month with 2,500 workflow executions, Cloud Pro at 50 euros a month with 10,000, and a Business plan at 667 euros a month with 40,000 that the page describes as self-hosted only. These are the annual-billing rates the page shows, and it does not state an effective date, so confirm before you budget. The page also notes that Business and Enterprise self-hosted features need a license key.

Two things follow for hiring. First, the software cost is small next to the build cost, so do not pick a developer to save a few euros on the plan. Second, decide on Cloud or self-hosted before you get quotes, because it changes the work: self-hosting adds server setup, updates and backups. Our n8n pricing breakdown covers how executions are counted and when self-hosting makes sense.

Where to find an n8n developer

n8n links a directory at experts.n8n.io from its site, and describes it as connecting businesses with experienced teams. The company also runs an Expert Partner Program for agencies, which as of today it describes as a closed pilot with an application and assessment process. We cannot tell you how listings in the directory are ranked or vetted, because the page does not say. Treat a listing as a starting list and run your own checks.

Beyond that, freelance marketplaces and the n8n community forum both surface people who build with it. The same vetting questions apply everywhere.

Red flags we would walk away from

• A fixed quote given before anyone asked what systems the workflow touches.
• Only template screenshots, no description of a failure or a fix.
• The workflows would live in the builder's own n8n account.
• No mention of error handling, testing or handover anywhere in the proposal.
• A promise that AI will handle the judgment calls with no human check on the output.

What we would do

If the job is one flow with clean inputs, we would hire a freelancer, run the five questions above, and insist on an error alert and a handover call. If the job spans a CRM, scheduling and billing, or an existing mess needs sorting before anything new is built, we would look for a team that audits first and builds second, and that gives you full access to the instance on day one.

Either way, pay for a small first milestone before committing to the whole build. A short paid scoping step shows you how the person communicates and how they handle the first thing that goes wrong, and that tells you more than any portfolio. If you want to see how we would approach yours, take a look at our n8n services page.