n8n · Zapier · Make: repair work
Order intake in n8n, repaired: every order is kept, and the team hears about every stop
A small ceramics studio sends orders from its shop to Google Sheets, a confirmation email and a Slack channel. After the repair, each order is handled once: one row, one confirmation, and a message to the team whenever a person is needed.
This page shows the repair: what was found, why it happened and what the fix changed. Both versions of the workflow are replayed over the same shift, so every difference is counted by the run, not claimed.
Self-initiated demo. Palewood Ceramics is an invented company; the orders, customers and outages are generated by a scenario file that ships with the project. The workflow JSON, the defects and the repairs are the kind of defects and repairs this service covers.
What the owner reported
Four observations from the owner, each with its own cause.
Every order in the sheet
Every order now reaches the sheet or is set aside for a person to check.
One confirmation per customer
Each customer now receives one confirmation, and an edited order updates the existing row.
Every stop reported in Slack
Any stopped run now sends a Slack message naming the node and the execution.
A manual check of every order
The automation was still running, and the manual check of every order took the time it was meant to save.
The same shift, run by run.
Before · Order intake v3
- Rows written to the sheet
- 0
- Interrupted runs
- 0
- Alerts sent to Slack
- 0
Outside the sheet:
After · Order intake v4
- Rows written to the sheet
- 0
- Interrupted runs
- 0
- Alerts sent to Slack
- 0
Outside the sheet:
Replay the same shift through both versions
One five-hour shift: 120 orders, 60 scheduled runs and the same test events for both versions: a seven-minute shop-host restart, one rate limit and one bad gateway from the shop API, two Gmail quota blocks, three orders the shop published seven to nine minutes late, four customers who corrected their order a few minutes after placing it, one order without a surname, one without a phone number, one with an empty email field, and one address that bounces permanently. The two workflow files are the only difference between the runs.
Before: “Order intake v3”
order-intake-v3.jsonAfter: “Order intake v4”
order-intake-v4.jsonWhat was broken, and why
Six defects. The “before” and “after” snippets are read out of the two workflow files on this page (not retyped), so they cannot drift from what actually runs.
Every run of the shift
Every scheduled run of the shift, listed the way n8n lists its executions. Rows in red mark the v3 runs whose stop was seen only in n8n.
| Run | Time (UTC) | Status | Saved | Parked | Emails | Alerts | Details |
|---|---|---|---|---|---|---|---|
| Run the comparison above to fill the log. | |||||||
How this page runs the workflows
So that nothing here has to be taken on trust.
- The two JSON files are written in n8n’s export format (node types, typeVersions, resource locators, retry settings and error outputs) and are meant to be loaded with Workflows → Import from file. To be exact about it: they were written for this demo and have not been opened inside a running n8n instance, so treat the canvas as untested and the logic as tested. The nodes, the expressions and the JavaScript inside the Code nodes are what you see in the snippets above.
- The page executes those files. A small runner in
engine/runner.jswalks the same nodes and connections, evaluates the same{{ … }}expressions and actually runs the JavaScript stored in the Code nodes. The shop API, Google Sheets, Gmail and Slack are local mocks with scripted outages. - Both versions get the identical shift. Same orders, same timestamps, same outages, same virtual clock, so retrying two seconds apart cannot escape a seven-minute outage.
- It is not n8n itself. The runner covers the nine node types these workflows use (Schedule Trigger, Error Trigger, HTTP Request, Code, Split Out, IF, Google Sheets, Gmail and Slack) and does not reproduce n8n’s queue mode, concurrency or its UI.
- One n8n quirk to know before testing it there: the cursor and the memory of handled orders live in the workflow’s static data, which n8n keeps for production executions of an active workflow, not for manual runs from the editor. Pressing “Execute workflow” by hand will therefore look as if the cursor never moves.
- One difference worth naming: the runner retries the item that failed. n8n retries the whole node, which can repeat items that already succeeded. For a node with a side effect (sending email), the production build therefore loops over orders one at a time, so a retry cannot email anyone twice. That loop is the next step recommended in the written repair report (available on request), not something this replay pretends to prove.
- The numbers in the panels come from the run you just triggered, not from
text written into the page. In the project,
node tests/run-tests.jschecks the same figures from the command line: 38 assertions over the files and both runs.
What the monthly part covers
- Watching the runs. Every stopped execution and every alert goes to a channel Flow Lab reads, so Flow Lab sees each stop before a customer does.
- Keeping up with the services. Flow Lab follows changes to the APIs and limits of the shop, Google and Slack.
- Small changes as the business changes. A new product type, a second sheet, an extra notification: all included, within the agreed monthly hours.
- A short monthly note: how many orders went through, what needed attention and what Flow Lab changed. One page in plain language.