How to hire an n8n developer

What does an n8n developer do?

An n8n developer builds automations: workflows that move data between the tools a business already uses, add logic where the tools do not, and keep running without someone clicking through them.

Most of the work I do in n8n is one of these: sorting enquiries and routing them to the right person, reading documents and pulling out the fields that matter, syncing a shop with a warehouse or an accounts package, building a daily report from several systems, or putting an AI step behind a human approval.

What should I ask before hiring one?

These ten questions tell you more than a portfolio.

• Where will the workflow run: n8n's cloud or a server you control?
• Who owns the n8n account and the workflow files?
• What happens when a step fails: retries, an error workflow, and who gets told?
• What happens if the same record arrives twice?
• Where do the credentials live, and who can read them?
• How is the workflow tested before it touches real data?
• What will it cost to run at my volume, including the n8n plan and any model calls?
• What breaks first when the volume grows, and what does fixing it involve?
• Can I export everything if I stop working with you?
• Who fixes it when it breaks after launch?

What does an n8n build cost?

I quote one fixed price after a free call, the same as any other build: a written plan of the workflows and the failure cases, then a price. Small jobs start at $50, like a single workflow or a fix.

The build is one bill. The running costs are separate, and they are the part most quotes leave out.

n8n cloud or self-hosted?

Both are n8n. The difference is who looks after the machine.

What does a bad n8n build look like?

The failures repeat, which makes them easy to spot once you know them.

• No error handling, so a failed step disappears and the work it was doing never happens.
• One enormous workflow with no notes, which nobody else can safely change.
• Credentials in a shared document or a message thread.
• No retry logic, so a flaky API creates duplicates.
• An AI step that sends customer messages without a person approving them.
• No log of what came in and what went out, so a wrong result cannot be traced.
• Built in the developer's personal account, with no handover.
• No export, so leaving means starting again.

How I work on an n8n job

If Zapier or Make is the better fit for what you need, I will say so, and the comparison guide explains why.

• The workflows and the failure cases are written down before anything is built.
• It is built in an n8n account in your name, so you keep it.
• Every workflow gets an error path, a log and an alert to a person.
• I test it with your real sample data, then with the cases that usually break: empty fields, duplicates, timeouts, a model returning nonsense.
• You get a written handover, and a support plan if you want someone on call.

Do you need a developer, or can you do it yourself?

n8n rewards people who can think in steps and conditions. If the workflow is simple, the volume is low and you have the time, the tutorials are good and you can get a long way.

Hire help when the workflow touches money, customer data or a deadline. Those are the places where a quiet failure costs more than the build.

What to remember

• Ask where it runs, who owns it and what happens when a step fails.
• A good build has an error path, a log and a person who gets told.
• The build is one bill; the plan, server and model calls are another.
• If you cannot export it, you do not own it.