---
title: "Comment by Ascendra Ventures on \"I replaced my daily admin with three n8n workflows. The AI was the easy part.\" | Hashnode"
description: "The two rules are the part I agree with most: the model only fills fields and never decides what happens next, and nothing it produces reaches a person without"
url: "https://hashnode.com/posts/i-replaced-my-daily-admin-with-three-n8n-workflows-the-ai-was-the-easy-part/6afcc5bdd280c719e1f90efd/comment/6afd11bfce409c14792a6d8f"
---

[Discussion](https://hashnode.com/posts/i-replaced-my-daily-admin-with-three-n8n-workflows-the-ai-was-the-easy-part/6afcc5bdd280c719e1f90efd)

Comment [I replaced my daily admin with three n8n workflows. The AI was the easy part.](https://hashnode.com/posts/i-replaced-my-daily-admin-with-three-n8n-workflows-the-ai-was-the-easy-part/6afcc5bdd280c719e1f90efd)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[1h ago](https://hashnode.com/posts/i-replaced-my-daily-admin-with-three-n8n-workflows-the-ai-was-the-easy-part/6afcc5bdd280c719e1f90efd/comment/6afd11bfce409c14792a6d8f)

The two rules are the part I agree with most: the model only fills fields and never decides what happens next, and nothing it produces reaches a person without a human pressing send. The bugs you list are the real ones too, from the fetch that returns a JavaScript shell to the loop that quietly handles one item out of six and the schedule nine hours late because the instance runs on UTC.

There is a similar story behind one of our case files at Ascendra Ventures. A global IT services firm had three internal problems at once: desk booking for an office with fewer desks than people, recruitment tracked across inboxes and spreadsheets, and performance reviews in yet more spreadsheets. Instead of three SaaS subscriptions or a full-time engineering team, one lean team shipped all three on Power Apps and Power Automate over SharePoint lists and SQL, each in about three months, and the operational spreadsheets were retired. Different tools from n8n and no model in the middle, but I think it supports your point that most of the value is in the dull, reliable parts.

Of the eight workflows you built, which one needed the most rebuilding once it ran on someone else's instance?
