Map the manual process into triggers, transformations, decisions and side effects before designing an n8n workflow. This gives you a reviewable business specification instead of a diagram that merely reproduces today's habits.
Describe the work without naming tools
Write one sentence stating the intended outcome, such as: “Turn an approved internal purchase request into a supplier instruction.” Then identify the person responsible for that outcome and the evidence that proves completion.
n8n documentation describes a workflow as connected nodes that automate a process. That supports thinking in connected steps, but it does not decide which business steps belong in your process. The mapping method below is editorial advice, not a promised platform feature.
Build a four-part process inventory
Give every activity a numbered card with its input, output and owner. Classify each card:
- Trigger: the event that makes work eligible to begin.
- Transformation: a calculation or reformatting that changes data without changing an external business state.
- Decision: a rule that chooses the next route.
- Side effect: an action such as sending an instruction or creating a record elsewhere.
Split mixed activities. “Check the amount and send the request” contains both a decision and a side effect. Keeping them together makes it harder to explain what happened when only one part succeeds.
Record manual judgement explicitly rather than hiding it inside a card called “process request.”
Try a hypothetical purchase request
Consider a fictional Pune studio processing synthetic request PR-104. Inputs are quantity 4, unit cost ₹750, approval status “approved” and a fictional supplier reference.
The inventory might read:
- Trigger: approval becomes final.
- Transformation: calculate the ₹3,000 total.
- Decision: confirm the supplier reference exists and the total matches the approved amount.
- Side effect: create one purchase instruction.
- Completion evidence: store the instruction reference against PR-104.
Evaluate the map with three variations: missing supplier reference, approval withdrawn, and an instruction already created. Each variation needs a named route and an owner. Do not use real supplier or customer records for this exercise.
Decide whether the map is ready
Stop if any side effect lacks an owner, a completion signal or a response to uncertainty. Next, ask someone who performs the work to walk through the cards without explaining them yourself. Only translate the map into connected nodes after that walkthrough succeeds.
If access procurement is next, check the automation catalog for access format and saved terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence.
Sources and scope
Source material checked 29 October 2026; features/policies may change. n8n workflow documentation establishes the connected-node workflow model and execution-history context. The inventory, purchase example and readiness criteria are editorial process-design advice, not documented implementation guarantees.