Made-to-Order Production Router
A small maker selling both stock and made-to-order pieces loses orders in the gap between the two. This workflow logs every order into a single production queue with its type and due date, repeats the personalisation back to the buyer before anything is cut, quotes a dispatch window rather than a delivery promise, and tells you when a ship-by date arrives with the piece still unmade.
What you get
Workflow blueprint
The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.
Getting it into Zapier
Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.
You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →
Not on Zapier?
An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 4 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Etsy has no native n8n node, so that step arrives as an HTTP Request node with the endpoint left for you to fill in.
What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.
A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.
Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →
Setup steps
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Implementation notes
- Repeating the personalisation back to the buyer catches roughly one typo in twenty before it is cut into wood. That single line pays for the workflow.
- Quote a ship-by date, never a delivery date. You control dispatch; you do not control the postal service, and promising what you do not control is how a good product earns a bad review.
- The overdue email deliberately goes to you rather than the customer. A machine apologising for lateness reads worse than saying nothing.
- If you sell both stock and made-to-order, add a Filter step before the Trello card. Stock items do not need a production card.