Workflow check for your automation pilot
Review process boundaries, duplicate execution, uncertain outcomes, human review and recovery. Download your pilot preparation.
A workflow succeeding once says little about everyday operation. This check prepares a pilot that includes repetition, outages and exceptions. The next steps respond to the answers you provide.
Choose one process with a clear beginning and end, such as recording an accepted enquiry in a CRM and preparing an internal task. Use a separate draft for another data flow. This keeps each control connected to the step it is intended to cover.
Prepare your plan
Your answers stay in this page. Download the draft to keep it; closing or resetting the page clears your input.
What do the answers mean?
“Yes, agreed” means you have examined the condition and arranged it with the people involved. It does not prove a technical control works. “Not known yet” remains an open question. Select “not needed” for human review only when you can explain why the bounded action may proceed without it.
The result is a preparation order. An unknown recovery path produces a concrete recovery test as a next step. The tool does not calculate a score that trades failures against completed answers. One unmanaged step can matter more to a particular workflow than several completed fields.
Test more than a successful run
Illustrative example: an enquiry first creates a CRM record, then a task. The second step fails. Restarting everything might create another CRM record. A useful pilot demonstrates that the same enquiry remains identifiable and only the missing task is recovered. The design might use a stable enquiry reference and a lookup in the target system.
Another test covers an uncertain outcome. After a timeout you do not know whether the other application created the task. Blind replay may create a duplicate. Agree how to find an existing task and when a person must decide. A technical error and a business outcome that remains unknown require different next steps.
Keep the pilot bounded and assess the real work
Measure current manual handling, review and recovery effort. Compare the pilot using the same definition. Include staff time spent handling exceptions and maintenance. Less data entry is useful only if the remaining working process is understandable and workable.
Download the draft and agree the sample, stop conditions and owner. Record when to roll back the pilot and how to handle unfinished cases. This tool does not run a workflow or connect to other software; use its output to design the actual pilot.
Understand the decisions behind your plan
n8n & process automation ↗Which business process should you automate first?
Choose a first automation using evidence about volume, handovers, exceptions and useful outcomes. Includes a worked selection example.
Read the guide ↗02 / n8n & process automationn8n, Make or Zapier: which fits your business process?
Compare n8n, Make and Zapier using a real workflow: supported actions, exceptions, maintenance, cost and handover. Includes a practical evaluation plan.
Read the guide ↗03 / n8n & process automationWhat does workflow automation cost? Budget beyond the initial build
Budget for workflow automation using discovery, integrations, testing, maintenance and review. Includes a transparent fictional calculation.
Read the guide ↗04 / n8n & process automationn8n Cloud or self-hosting: what must your business organise?
Compare n8n Cloud and self-hosting through responsibility, access, data flows, recovery and maintenance. Includes a fictional decision example.
Read the guide ↗05 / n8n & process automationA failed n8n workflow: investigate and recover without duplicate actions
Investigate failed workflows using execution evidence, business references and checks on earlier actions. Includes a detailed fictional recovery case.
Read the guide ↗06 / n8n & process automationHuman approval in workflows: make authorisation meaningful
Design human approval around authority, a specific data version, expiry and controlled execution. Includes a fictional purchasing example.
Read the guide ↗07 / n8n & process automationDesigning an automation pilot: evidence for the next decision
Plan an automation pilot using representative cases, observable acceptance, human review and stopping conditions. Includes a fictional trial design.
Read the guide ↗08 / n8n & process automationMaintaining n8n workflows: ownership, checks and controlled change
Organise workflow maintenance around ownership, meaningful checks, updates, access and handover. Includes a fictional business-rule change.
Read the guide ↗