Flow Lab

Every order accounted for in n8n

The reworked n8n workflow delivers every order to the spreadsheet, the customer and the team's Slack on its own. In the demo, all 120 orders in the shift are accounted for. Reworking one of your n8n, Make or Zapier workflows costs $150. You get a price and a timeline within one business day.

This demo is self-initiated, with no client behind it. Palewood Ceramics is an invented company. Every figure about the demo comes from the demo itself, so you can open it and check each one.

Screenshot: the reworked n8n order intake

Figures from the demo run (invented business)

120 out of 120orders in the shift accounted for
60 out of 60scheduled runs completed
4alerts, only where a person is needed
45automated checks confirm every figure
How the order intake was reworked.

The demo shows how the reworked n8n workflow takes every shop order to the right place. A reliable automation works quietly in the background, so the business owner has more time for customers and the work itself.

The demo is built around Palewood Ceramics, an invented pottery studio whose n8n workflow sends each shop order to three places. Those places are an order spreadsheet, a confirmation email to the customer and a Slack channel for the team. After the rework, each order becomes one row in the spreadsheet, one email to the customer and one Slack message for the team.

First, a typical shop shift is recorded and rebuilt so it can be replayed again and again. The shift holds 120 orders over 5 hours and 60 scheduled runs. It also includes the usual day-to-day events of a shop. During the shift, the shop's site restarts, the email service reaches its daily limit and some orders show up a few minutes late. Some customers update their address after ordering. The shift also includes orders with incomplete details. The reworked workflow handles every one of these situations.

120 out of 120orders in the shift accounted for after the reworkFigure from the demo run (invented business)

The new version ran through the same shift in full, from the first order to the last. All 120 orders in the shift were accounted for. Each of the 60 scheduled runs completed.

Run log of the previous version, run by run.
Run log of the previous version, run by run.

Each improvement adds to the result, and together they bring the count to 120 orders out of 120. When the shop's site restarts, the workflow retries the request, so the run completes. The workflow fetches orders from an exact timestamp, so orders that show up a few minutes late reach the sheet too. Each order is written to the sheet once. An order where the customer gave only a first name goes down a separate path. The Slack message goes out independently of the email, so the team sees every order in the channel.

The new version remembers exactly where it stopped and advances its timestamp only once an order is safely saved. So every order reaches the sheet, even when a run starts over. It also remembers which orders it has stored, so a repeat of the same order stays as one row. When a customer updates an order, the new version writes the change into the same row, and the team is notified. The customer gets a single confirmation email.

The workflow checks orders one at a time and passes any order that needs attention to a team member in Slack. Every event that needs a person becomes an alert that says what happened and where. The API key lives in the credential store, separate from the workflow file.

One change, previous and new workflow side by side.
One change, previous and new workflow side by side.

By the end of the same shift, each order was written to the sheet once. Each confirmation email went out to the customer once. The team received 4 alerts, each about an event that truly needed a person.

Every figure can be checked. The demo page replays both workflows against the same shift right in the browser, in under a second. It shows what each version did, run by run. 45 automated checks confirm that the previous workflow matches its description and that each change was actually made in the new one. The same checks confirm that every figure on this page comes from the runs. The report on the demo page also names what is worth doing next. It explains how the browser replay differs from n8n itself.

The report on a narrow screen, light and dark theme.
The report on a narrow screen, light and dark theme.

In a real project, you get the reworked workflow and a plain-language explanation of each change. Your busiest week is replayed through both versions, so you see the result on your own orders.

Reworking one workflow with a short report costs $150. Reworking several workflows or rebuilding an automation costs $600 to $2,400. That work takes 1 to 4 weeks. I quote the exact price and timeline once you describe the task.

All amounts are in US dollars. You pay for each stage after you approve it. You can pay each stage via Contra, a PayPal invoice or crypto.

The work happens in Claude Code, Anthropic's AI coding tool. After the AI drafts the changes, I run the checks and replays myself. Work starts 2 business days after you confirm the quote. Your quote holds for 7 days.

Optional support after handover costs $150 a month. It covers up to 6 hours of work a month. Support requests get a reply within one business day. You can cancel support month to month.

Your order includes one small extra automation, up to 30 minutes of work, at no charge. This applies if you confirm the quote within 7 days.

Next step

A review of your workflow.

Within one business day, you get a review of your workflow with a price and a timeline. The review is free. To request it, send a screenshot or a short recording of your workflow, with one line on the result you need. Any bug found within 30 days of delivery is fixed at no charge.