Hiring someone to build in n8n is easy. Hiring someone whose workflows are still running properly six months later is the hard part. When an automation goes wrong, the idea is rarely the problem. The usual causes are a flow with no error handling, no notes, and one person who knows how it works.
This checklist is for founders, operations leads and agencies outside the n8n world who need to judge a freelancer or agency quickly.
What an n8n developer actually does
The visible part is building workflows: a trigger, some steps, a few API calls. The part that decides whether the project works is everything around it:
- choosing between n8n Cloud and a self-hosted server, and setting that server up safely;
- handling errors, retries and alerts, so a failed run is noticed the same day;
- keeping API keys and passwords out of the workflow itself;
- writing down what each flow does and who to call when it stops;
- keeping costs in check when a flow calls an AI model.
If the conversation only covers the first part, you are hiring a builder, not someone who will run it with you.
Seven questions to ask before you sign
- Where will n8n run, and who keeps it updated? n8n Cloud means n8n looks after the hosting. Self-hosting means someone has to apply updates, take backups and watch disk space. Ask who that someone is and how often they do it. Our n8n vs Make vs Zapier guide covers the trade-off.
- How will I know when a workflow fails? n8n lets you attach an error workflow that runs when another one fails. Ask what it does: an email, a Slack or WhatsApp message, and to whom. "We check it now and then" is not an answer.
- Where are credentials stored? They belong in n8n's credentials store, which is encrypted with an encryption key you should hold a copy of, not pasted into Code nodes or HTTP headers in plain text.
- Who owns the account and the workflows? The n8n instance, the WhatsApp, CRM and accounting accounts should be in your company's name. Workflows can be exported as JSON files; ask for an export of everything at handover and keep it with your other company documents.
- How are changes tested? A sensible answer includes a copy of the workflow or a test instance, sample data, and a rule that nothing is edited live on a busy afternoon.
- What happens when an AI step gets it wrong? If a flow uses Claude, GPT or Gemini, ask what the model is allowed to do on its own, where a person reviews the output, and what monthly cost limit is set.
- What do I get in writing? At least a one-page note per workflow: what starts it, what it changes, what to do when it fails. If they leave, someone else must be able to pick it up.
Red flags
- The workflows will live in the developer's own account "for now".
- A single workflow that does everything, so one failure stops all of it.
- No mention of error handling until you ask.
- A price for building, but no word on who maintains it afterwards.
- Promises of exact hours saved before anyone has looked at how your team works today.
Freelancer, agency or someone in-house?
| Freelancer | Agency | In-house | |
|---|---|---|---|
| Best for | One or two clear workflows | Several flows, AI steps, ongoing changes | Automation at the centre of your operations |
| Watch out for | One person holds all the knowledge | Who on their team will actually do the work | Hiring takes time, and one person still needs backup |
| Ask for | Documentation and an export at handover | A named person and a maintenance plan | A second person trained on every flow |
There is no right answer for everyone. A small business with three flows does not need an agency, and a SaaS company running onboarding and billing on n8n should not depend on one freelancer.
A good first project
Start with one workflow that runs often and is easy to check, such as replying to new leads or sending payment reminders. It shows you how the developer works, how they document and how they handle the first failure, before you trust them with anything bigger. Count how many hours your team spends on that task today, so you can tell whether it worked.
How we work
Makani Tech, based in Surat, Gujarat, builds and maintains n8n workflows in the client's own accounts, with error alerts, a run log and a note for every flow. The work is led by Kishan Makani, who has 14 years in tech. See n8n automation for what is included, or workflow automation if you are still choosing a tool. Free n8n templates and guides are in Resources.
Questions people ask
How much does it cost to hire an n8n developer?
It depends on the number of workflows, the apps involved and whether you need ongoing maintenance. Ask for a price per workflow, a separate monthly price for hosting and maintenance, and the expected running costs of any paid APIs, so you can compare quotes on the same terms.
Do I need n8n Cloud or a self-hosted server?
n8n Cloud is simpler: n8n handles hosting and updates. Self-hosting gives you control over where your data lives and no per-execution charge, but someone has to maintain the server. If nobody on your side can do that, include it in the developer's maintenance plan.
Is an n8n certification or badge enough to judge a developer?
n8n publishes its own courses, and finishing them shows the person knows the basics. It does not show how they handle errors, security and handover. Ask to see a workflow they built and still maintain, and how they would answer the seven questions above.
Can an n8n developer work remotely?
Yes. Everything is done through the n8n editor and your apps' web dashboards, so location matters less than clear access rules: give them their own login, never a shared password, and remove it when the work ends.
Written by Kishan Makani
Founder of Makani Tech, 14 years in the tech industry. Builds AI automation and mentors people who want to build their own, from Surat.

