I Followed WorkBuddy's Batch Document Guide and Cut It Down to Three Steps
Community Discussion · General

I Followed WorkBuddy's Batch Document Guide and Cut It Down to Three Steps

SleepySleepy4d ago2026/11/15 190 views

Last night I was about to sleep when I scrolled onto an article about WorkBuddy workflow orchestration and batch document processing — resume screening, structured extraction, auto reports, all lined up. After reading I was very sleepy, but I sat up straight. Because there was a pitfall in it I'd just stepped into last week. Instructions written too vaguely, the AI fires back a bunch of questions, several rounds back and forth, credits doubled.

The article's scenarios were HR and operations. Mine is a counseling office — client records, parent notification templates, month-end reimbursement summaries, plus Tencent Meeting transcripts to organize into minutes. Different scenarios, same principle: break repetitive work into reusable molds. Like movable type printing — one character mold can be set again and again.

After breaking it down, only a third was directly usable, but the time saved was more than I expected.

My environment is macOS desktop, used for about a month, version may differ from yours — if paths don't match, look for a similar entry point.

The authorization step is where things most easily go wrong. In Settings → File Access → Add Directory I added a workspace folder, chose "this folder only," didn't check "include subdirectories." The reason I stress this is because the first time I took the easy route and authorized all of ~/Documents, and it scanned the counseling office archive directory from top to bottom — watching the progress bar made me a bit nervous. Things like client records shouldn't be casually read in by a batch task.

After creating the directory, go back to the main interface and click New Task, choose mode Craft. This executes immediately, doesn't repeatedly confirm with you. There's another mode next to it that asks a few questions first before acting — suitable when you yourself haven't thought it through. I only use Craft once I've thought it through.

I write instructions following five elements: file path, processing action, processing dimension, output format, output filename. Miss one and it fires back a question, and a question is a round of credits. One I actually wrote was roughly like this:

Read all PDFs and screenshots under ~/workspace/2026-11 reimbursement/, extract amount, date, merchant name, sort by date, output Excel to ~/workspace/2026-11 reimbursement/summary_202611.xlsx

It ran about four minutes. A dozen or so receipts, two crookedly photographed ones had amounts misrecognized, I fixed them manually. Image quality is a hard threshold, can't get around it.

I'm fairly cautious with sharing. Don't put original records in the shared directory — original records stay local, the shared directory only holds desensitized templates and summary tables. The operation is Share → New Shared Space → Invite Members, permissions split into viewable and editable. I gave my assistant viewable, only the summary table subdirectory set to editable. She can't change the original stuff, and won't accidentally delete it.

On operations, a few things I learned the hard way. Only let it do one thing at a time — I once tried stuffing minutes organization, to-do extraction, and weekly report generation into one instruction; the output was wrong, had to rerun, credits wasted. Fix the output filename with a month suffix — by default it often calls it summary.xlsx, and the second run overwrites the previous one. And spend ten minutes each weekend manually reviewing the output. Entries in the middle paragraphs of long documents get mixed up — I mentioned this in the forum last month, and later learned to split a document into separate files before feeding them in.

This thing didn't make me more diligent. I still drag it out until the last day of the month. But it lowered the cost of starting — before it was a whole evening, now half an hour. As a psychological counselor I diagnosed myself, and the conclusion is: hopeless. Tools can't save you from procrastination, only save you time.

2 replies

?
Ctrl + Enter to reply
Zhe Dan Bai De

A dozen-plus receipts and two come out wrong—image quality is the same hard threshold in biological data; AI can't get around the dirty data of wet-lab experiments either.

Terminology Police

"From 'Movable Type Printing' to today—you mentioned 'feed it in as a separate file,' and this detail really is key: for long documents, the middle paragraphs are processed serially, which is essentially a context window and batch scheduling problem; splitting is the most reliable workaround."