How to Hire an n8n Developer

Ask about the failure, not the diagram

Anyone can connect a form to a spreadsheet. The work that matters shows up in three places: what the workflow does when an API times out, how it avoids creating the same person twice, and whether a human is told when a run dies overnight.

If a candidate changes the subject to AI agents when you ask about retries, you are talking to a demo. A working answer mentions an error path, the original payload kept so it can be replayed, and an alert that is not the same inbox nobody reads.

Five questions for the first call

You can ask these in fifteen minutes:

• What has to be true before you will quote — volume, the system of record, and what counts as a duplicate?
• Where does a failed run go, and who is told?
• Will the n8n instance and the credentials stay in my accounts?
• What does handover include besides the workflow file?
• What is deliberately out of scope on this first workflow?

What a first engagement should be

Do not hand over the whole operation. One workflow, two tools, a written field map, and a failure notification is a complete first job. On this site that is the Basic automation package, from $120, usually a few working days.

The next step, if the first one holds, is every lead source feeding one CRM record, with de-duplication and a dated follow-up. That is Standard, from $250. Branching, safe retries, and a view of what ran are Premium, from $450.

Ownership is part of the price

The workflow should run in an account you can revoke. If the only copy lives in the developer’s n8n, you have hired a dependency. Documentation is how you leave: what triggers it, what it writes, and what to do when a run fails. A quote that arrives before those questions is a price for a deposit, not for a system.