Choosing an n8n partner starts with the work your team needs to complete, the systems involved and who will look after the workflow. Use these questions to compare proposals before agreeing to an implementation.
Complete fields allow the delivery step. The office still needs a named person to review the request.
Stop before delivery when a reply detail is missing. A person decides whether there is a suitable way to clarify it.
Keep the failed request visible. Check what was accepted before retrying so that a repeat attempt does not silently create a duplicate.
Choose a case, then play its route.
Scripted planning illustration. No n8n instance, CRM or network service is connected.
Describe the work you want to automate
Write down what starts the work, what information is needed, who makes decisions and what should happen at the end. Include exceptions: incomplete details, duplicate requests, a service that is unavailable, or a person who needs to approve a result. If the process is still changing, simplify or clarify it before automating its steps.
Ask each provider to identify what n8n would do and what remains a human responsibility. n8n is one workflow automation option that can connect services through integrations and APIs. A native feature in an existing system, another integration platform, or a small custom application may fit better depending on the systems, permissions, volume and upkeep involved. Compare against your actual requirements rather than a general claim that one tool is best.
Compare proposals against the same checklist
| Area | Ask the provider |
|---|---|
| Inputs and access | Which apps and accounts are involved? What data and permissions are required, and who approves access? |
| Exceptions | How are missing fields, duplicates, API limits, outages and failed steps recorded and routed? |
| Ownership | Who owns the n8n environment, credentials, workflow definitions, backups, updates and recurring costs? |
| Support | Who sees an alert, decides whether to retry, and handles a change when a connected service changes? |
| Handover | Will your team receive access, a workflow map, operating instructions, recovery steps and a walkthrough? |
Prefer a proposal that states exclusions and assumptions clearly. Confirm whether each connected service permits the required API access on your plan; a connector cannot bypass a vendor's permissions or data rules. Ask how the design avoids exposing credentials and limits access to the records each step needs.
Agree on acceptance criteria with an example
Consider a fictional process that receives a service enquiry, checks required fields, creates a record and assigns a person to review it. A useful acceptance discussion might ask for these outcomes:
- A complete new enquiry creates one record with the agreed fields and an assigned reviewer.
- An enquiry missing a required field is flagged for a person to resolve, not silently discarded.
- A repeat submission is identified according to an agreed rule, with no unintended duplicate record.
- If a connected service is unavailable, the failure is visible to a named owner and can be safely reviewed before retry.
- The team can inspect the outcome and knows how to pause the workflow if its output looks wrong.
These are proposed checks for a hypothetical workflow, not results from a deployed system. Ask the provider to demonstrate each agreed case in a test environment using suitable sample data, then record what counts as a pass before live access is considered.
Settle hosting and licensing before choosing a model
n8n documents cloud and self-hosting options. Hosting changes who operates the infrastructure: self-hosting brings responsibilities such as security configuration, backups, updates and availability. Ask who handles these tasks, where credentials and data reside, how access is removed, and what happens if the provider relationship ends.
Check the license against the exact delivery model: n8n's current guidance says its self-hosted Community edition can be used to build and run client workflows on a provider's own instance when customers only receive the outputs and cannot access the editor or change the workflow logic. If customers outside the provider's organisation can build or configure workflows, or n8n is hosted as a service or white-labelled, a commercial license is required. Installing and managing n8n on the customer's own server is a separate case; the customer chooses the license that applies to their use. n8n Cloud has separate subscription terms. Read the current n8n license FAQ and ask n8n to confirm the proposed model before agreeing to it. These terms may change; self-hosting by itself does not settle licensing.
Plan handover and ongoing support
Before work begins, name the person in your organisation who approves workflow changes and receives failure alerts. Agree on how the provider will transfer environment access, document connections and field mappings, explain routine checks, and train the person responsible for first response. Clarify whether future fixes, monitoring and changes are included in the proposed engagement or need a separate arrangement.
Bring an existing spreadsheet, a few sanitised example records and a sketch of the current steps to a scope discussion. For broader process planning, see workflow automation. The office workflow sample is an illustrative local demonstration; it is not connected to n8n or a live business system. To discuss your requirements, use the contact page.