Anyone can build an n8n workflow that works in a demo. You want someone who builds one that still works six months from now, when an API changes and the person who requested it has moved on. These ten questions help you tell the two apart.
Why the hire matters more than the tool
n8n is powerful because it’s open-ended. You can connect almost anything, add AI steps, write code and self-host. That flexibility cuts both ways. A careful builder gives you clear, documented workflows that your team can run. A careless one gives you a tangle of unnamed nodes that only they understand, and a bill every time something breaks.
The business case for hiring well is simple. Workflows usually sit in the middle of things that matter: leads, invoices, customer messages, reporting. When they fail silently, you lose money before anyone notices. The questions below are the ones I’d ask if I were on your side of the table. I’m an n8n consultant, so take that into account, but these are the standards I hold my own work to.
The 10 questions
1. “Can you show me n8n workflows you’ve built?”
Look for real examples: published templates, screenshots, or a screen share of a workflow with client data blurred. Published n8n.io templates are a good sign, because n8n reviews them before they go live. Good answer: specific workflows, with an explanation of why they were built that way. Red flag: only logos, or only Zapier work.
2. “What questions do you have about our business before you talk about tools?”
A good developer asks what the task costs you today, who does it, how often it happens and what “done” looks like. If they jump straight to nodes and AI, they’re selling a build, not solving a problem.
3. “How will you handle errors and failures?”
Every production workflow fails sometimes. An API times out, a field arrives empty, a token expires. Ask how they’ll know. Good answer: an error workflow that alerts a named person by email or Slack, retries where it’s safe, and a log of what failed. Red flag: “It won’t fail.”
4. “Where will the workflows and credentials live?”
They should be in your n8n instance and your app accounts, with credentials stored in n8n’s credential manager, not typed into nodes. If the developer leaves, you keep everything. Be wary of anyone who wants to run your workflows on their own account.
5. “n8n Cloud or self-hosted, and why?”
There’s no single right answer, but there should be a reasoned one. Cloud is quicker and needs less upkeep. Self-hosting gives you more control over data and costs, but someone has to own updates, backups and security. Listen for whether they ask about your data sensitivity and your IT capacity before answering.
6. “How do you use AI inside workflows, and how do you keep it reliable?”
AI steps such as classifying emails, extracting invoice fields or scoring leads are where a lot of value is now. They’re also where workflows go wrong quietly. Good answer: structured output, clear rules in the prompt, testing on real examples, a fallback when the model isn’t sure, and a human approval step for anything that sends money or messages. Red flag: “The AI just figures it out.”
7. “How will we test it before it goes live?”
Ask for testing on your real data (or realistic samples), including the messy cases: the scanned PDF, the blank form field, the email in another language. A week running in parallel with the old process is a good sign of a careful builder.
8. “What will the handover look like?”
You should get clearly named nodes, notes on the canvas explaining each section, short written docs and a walkthrough, live or recorded. Ask to see an example of their documentation. If they can’t show any, assume you won’t get any.
9. “How do you price this, and what isn’t included?”
Fixed project, retainer and hourly are all legitimate. What matters is that the scope is written down. Ask specifically about changes after launch, the support window and running costs (n8n plan, AI usage, app fees). A clear proposal lists the one-time build cost and the monthly running costs separately, so you can weigh both against what the problem costs you now.
10. “What would you not automate here?”
This is my favorite question. A good developer will push back on something, maybe a step that needs human judgment, a process that should be fixed before it’s automated, or a job a simpler tool like Zapier handles fine. Someone who says yes to everything is optimizing for hours, not for your business.
Red flags, in one list
- No examples of n8n work they can show you.
- They want your passwords instead of setting up proper credentials.
- No mention of error handling, testing or documentation.
- The workflows would live in their account.
- A price with no written scope.
- Every answer involves more AI.
Before you reach out, prepare this
You’ll get a faster, more accurate proposal if you send:
- The task in one sentence (“when X happens, we need Y”).
- The apps involved and who owns each account.
- How often it happens and roughly what it costs you today.
- A sample input such as an email, a PDF or a form entry, with sensitive data removed.
- Who on your team will own the workflow afterward.
How I’d answer these
I’m Robert Breen. I teach n8n on Udemy to about 15,000 students, publish templates on n8n.io as a verified creator, and build n8n workflows and AI agents for small and mid-sized teams. I start every project with the business problem, build in your accounts, test on real data with you, and hand over a documented workflow with sticky notes on every section and a walkthrough. Past projects include a data pipeline that loads a field-service company’s software into BigQuery, and a route optimization that saved an electrical contractor about $1,500 a month.
If you’d like to put me through these ten questions, get in touch or read how I work as an n8n developer. You can also see everything I build.
Frequently asked questions
What should I look for in an n8n developer?
Real n8n examples you can see, questions about your business before tools, a plan for errors and alerts, workflows built in your own accounts, testing on real data, and clear documentation at handover.
Should the workflows live in my account or the developer's?
Yours. Workflows should run in your n8n instance with credentials stored in n8n's credential manager, so you keep everything if the developer moves on.
What are red flags when hiring an n8n developer?
No n8n work to show, asking for passwords instead of setting up credentials, no mention of error handling or testing, a price with no written scope, and an answer of more AI to every problem.
What should I send a developer before the first call?
The task in one sentence, the apps involved, how often it happens and what it costs you today, a sample input with sensitive data removed, and who will own the workflow afterward.
Want this built for your business?
Book a free 30-minute call. You’ll get a clear next step and a written quote before any work starts, even if the answer is a free course instead of a project.