How we connected Shopify, Airtable, and Gmail with n8n to eliminate 14 hours of weekly manual admin for a growing DTC team — and reversed a hiring decision in the process.
The founder of this DTC brand came to us with a specific number in mind: she was spending somewhere between two and a half and three hours every single day in her inbox and in spreadsheets. Not doing anything creative. Not talking to customers. Just moving information from one place to another — copying order details from Shopify into a shared Google Sheet, emailing suppliers when new inventory thresholds were hit, manually sending follow-up emails to customers whose orders had shipped. All of it done by hand, every day, because that's how it had always been done.
The ops team was three people, all capable, and all increasingly behind. Order volume had grown about 40% over the prior six months — a good problem, but one that exposed just how fragile the manual systems were. Errors were creeping in. A supplier would miss a notification because an email got buried. A customer wouldn't get a post-purchase follow-up because someone forgot to send it on a busy day. Nothing catastrophic, but the kind of slow friction that compounds over time and quietly erodes trust with both suppliers and customers.
The conversation that brought them to us was actually about hiring. They'd gotten to the point where the founder was seriously weighing bringing on a fourth ops person — not to do anything new, just to keep up with the existing volume. The job description was half-written. That's when a peer suggested they talk to us first.
When we did the initial call, it became clear quickly that this wasn't a capacity problem. It was a systems problem. The work itself was repetitive, rule-based, and almost entirely predictable. Every order followed the same path. Every supplier notification triggered from the same conditions. Every post-purchase email said roughly the same thing with a few order-specific details filled in. These were exactly the kinds of workflows that should be automated — not because automation is always the answer, but because a human doing this work at scale is a genuinely poor use of their time.
We started with a workflow audit before writing a single line of anything. That means sitting down — in this case over two Zoom calls and a shared Notion doc — and mapping every manual step that touched more than one system or more than one person. Not the steps people thought they were doing, but the steps they were actually doing. Those are often different, and the gap between them is usually where the problems live.
What we found was three clusters of manual work that, when you added up the time across the whole team, came out to roughly 14 hours per week. Order ingestion and tagging (pulling from Shopify, categorising by product line and region, flagging anything that needed special handling) was consuming about five hours per week across two people. Supplier communications — notifications when stock hit certain thresholds, order confirmations, reorder triggers — was another four hours, mostly fragmented across the day in ways that made it harder to measure but easy to underestimate. And post-purchase customer follow-up — shipping confirmations, delivery check-ins, review requests — was about five more hours of work that was being done inconsistently and, on busier days, not at all.
Once we had the map, we scoped the build. Three workflows, built in n8n, with Airtable as the operational database that sits between Shopify and everything else. The choice of Airtable wasn't incidental — the team was already comfortable in it, it gave them visibility into what the automations were doing without needing to understand the underlying logic, and it made the system auditable. If an order looked wrong or a supplier email didn't go out, they could check the Airtable record and trace what had happened. That kind of transparency matters, especially when you're handing off work that used to live in someone's head.
We built over three weeks. Week one was the Shopify-to-Airtable ingestion and tagging logic. Week two was supplier notifications and the reconciliation reporting. Week three was post-purchase email sequencing, testing across the full order lifecycle, and handoff. We ran a two-hour training session at the end so the ops team understood what each workflow did, how to check the logs, and what to do if something behaved unexpectedly.
The first workflow handles order ingestion. Every new Shopify order triggers an n8n flow that pulls the order data, auto-tags it by product type and shipping region using a set of rules we defined with the team, and writes a clean record into Airtable. High-value orders get a flag. Orders with multiple SKUs get a secondary check. Supplier notification emails go out automatically at the same time, using a template that pulls in the relevant order details — no manual composition, no copy-paste. The supplier gets the right information immediately, not when someone remembers to send it.
The second workflow is the post-purchase email sequence. It triggers off fulfillment status changes in Shopify. When an order ships, the customer gets a shipping confirmation with tracking information pulled directly from the order record. Three days after the estimated delivery date, a check-in email goes out. If delivery is confirmed, a review request follows seven days later. All of it conditional, all of it triggered without anyone touching it. The emails don't read like they came from a robot — the team reviewed the templates carefully and they reflect how the brand actually talks to its customers.
The third workflow is a weekly supplier reconciliation report. Every Monday at 8am, n8n pulls the prior week's order data from Airtable, aggregates it by supplier and product line, and emails a formatted summary to the relevant supplier contacts and the ops lead. What used to be a Friday afternoon task that frequently slipped into Monday is now done before anyone logs in.
The 14 hours per week came back immediately. That's not a projection — within the first full week of the workflows running live, the ops team tracked their time and the manual tasks were simply gone. The orders were in Airtable. The supplier emails had gone out. The post-purchase sequences were running. Nobody had touched any of it.
The more significant result came about six weeks in. Order volume continued to grow — up another 20% from the time we started — and the ops team of three handled it without adding hours or adding headcount. The workflows scaled with the volume. The hiring conversation was officially closed. The job description that had been half-written was deleted.
There haven't been any missed customer follow-ups since go-live. The supplier relationships have noticeably improved — one supplier specifically mentioned that the communication had gotten more consistent and that it made their planning easier. The founder is spending those reclaimed hours on sourcing, brand partnerships, and the parts of the business that actually require her judgment.
The ROI calculation is straightforward: three weeks of build work paid for itself within six weeks, accounting for the time savings across the ops team at their effective hourly rate. If you factor in the averted cost of a fourth hire, the payback period would be measured in days. But the number that the founder keeps coming back to is simpler than any of that: she stopped dreading Monday mornings.
"We were about to hire someone just to keep up with the admin. We didn't need to."
We start every project with a workflow audit. Book a call and we'll tell you honestly whether automation makes sense for what you're dealing with.