When Claude Belongs in an Automated Office Workflow
Reddit user /u/CrypoKings says they automate repetitive daily portal work with Python and browser automation rather than Claude. The workflow signs in, downloads reports, renames files, and files them where colleagues expect them; failures stop the run and trigger an email identifying the broken step. They reserve Claude or another model for judgment-dependent tasks such as reading messy invoices, sorting scanned forms, and naming files from inconsistent layouts.
The account offers a concrete division of labor between deterministic automation for repeatable steps and AI for steps that require judgment.
I set up automation for small offices. A lot of people ask me to "add Claude" to a morning workflow that is really just: log into a vendor portal, download yesterday's report, rename it, drop it in a folder, paste a few totals into a spreadsheet.
For that kind of job I usually don't put Claude in the loop.
The steps are the same every weekday. Most of these portals have no API, so I use Python and browser automation that signs in on a schedule, pulls the same report, names it the same way, and files it where the next person expects it. I care more about it running every day than about it being clever. If a login fails or a page moves, the run stops and emails which step broke instead of guessing.
Where Claude (or another model) does fit is the one step that needs judgment. Reading a messy invoice. Sorting a scanned form. Naming a file from what is on a page when the layout is inconsistent. I use AI for that step only and keep the login, download, rename, and file drop as plain automation.
I also say no a lot. If a task only happens a few times a year, or it takes real judgment every time, it usually isn't worth automating.
Curious how others here decide when Claude belongs in an office workflow versus when a script is enough.
submitted by /u/CrypoKings [link] [comments]