1
The email trips it
The boss's request arrives. The local agent recognizes it by sender and subject and starts the job — no clicking, no app to open.
A worked example
Sally stopped writing the Friday report. It still goes out every Friday.
One person, one recurring task she resents, and the AI plus agent that now handle it — while she does the job she's actually paid for. No new software for her to learn. She just told her Claude what she wanted.
The setup
Every Friday, the same email.
Sally is in sales. Her week is phone calls, client dinners, and the relationships that turn into contracts. And every Friday, the same email lands from her boss: "Need the TPS report by end of day." It's twenty minutes of copy-paste she resents — because those are twenty minutes she's not on the phone closing business.
She doesn't want a better report template. She wants the report to happen without her.
What she did
She didn't file a ticket. She asked her Claude.
Her company runs WorkflowHub, and IT had already set up two things for her: the WorkflowHub MCP, so her Claude can create and route real work items, and the local agent, so it can watch her inbox and send mail as her. Sally didn't know or care what either of those was. She just typed one sentence:
"When my boss emails asking for the TPS report, put the report together, log that you did it, and send it to him — but show me before it goes."
That was the whole configuration. Plain English, once.
The next Friday
What happens now, start to finish
Four steps. Only the last one reaches outside the company — and it waits for a human.
2
Proof of work
It creates a work item in WorkflowHub, logged under Sally — a record that the report was produced, by whom, and when.
3
It drafts
It assembles the report and drafts the reply with it attached. Nothing has left the building yet.
4
She approves, it sends
Sally gets a one-tap approval on her phone. She taps yes. It sends as her, and the whole run is on the audit trail.
The only step that reaches outside the company — the send — stopped for a human. That's the Golden Rule, and it isn't optional.
Then she got clever
The report she sends from a beach chair.
The agent watches a mailbox — it doesn't much care whose email trips it. So Sally added a second trigger: an email from her personal account, with a keyword she picked, fires the same job. Now she doesn't need her boss's email, or her laptop.
From a lounge chair at the company sales offsite, she thumbs a two-line email from her phone and the report goes to whoever she names — because the agent runs on a server IT set up, not on the laptop back in her hotel room. It never sleeps, and neither does her Friday report.
soon Want it to just run on a schedule — no trigger email at all? That's on the way: a timer on the agent that files the work item on its own, so even the reminder is automatic.
The part that matters
Why her boss — and her auditor — are fine with this
This is the difference between "I let an AI into my email" and something a compliance team signs off on.
Logged as Sally
Every work item and every send is attributed to her, in the audit trail. It isn't a mystery bot acting on its own — it's Sally, automated, and the record says so.
A human approves the send
The AI drafted and prepared everything, but nothing left the company without Sally's tap. There is no path for a rogue or prompt-injected instruction to send on its own.
Her credentials never moved
The mailbox access lives on the agent, on IT's server. WorkflowHub's cloud never sees her password — it can orchestrate the work without ever holding the keys.
Her boss gets his report on time. The audit trail proves it happened. And nobody handed an AI unsupervised control of her outbox to pull it off. That's the whole idea.
P.S. — the admin who wired all this up in ten minutes? Somebody get that person a nice stapler.
What's your Friday report?
Everyone has one — the recurring task that eats the hours you'd rather spend on real work. Point your Claude at WorkflowHub and hand it over.