The problem
Tasks don't arrive in a task manager. They arrive mid-run as a thought, as a screenshot of a job post, as a link someone sends. Opening the right app and filing things properly takes just enough friction that most of it evaporates.
Every productivity tool answers this by asking the user to change behavior, and that's the adoption bet enterprise software loses every day. A system that requires new habits loses to the messy channel people already use. The fix is meeting the input where it happens.
Who it's for
One user (me), one channel (WhatsApp), several downstream systems (Sheets, Calendar, Gmail). The shape, though, is the universal intake problem: a requester who won't fill out a form, systems of record that need structure, and an owner who pays for every dropped request in follow-up chaos.
Swap the nouns and this is the ops-team version a business leader would fund. Requests arrive by chat and email, an agent extracts the structure, rows land in the system of record, and the requester never leaves the channel they started in.
The approach
A WhatsApp number acts as the single capture point, built around an AI agent:
- Any modality in. Plain text, voice notes (transcribed with Whisper), or screenshots read by a vision model. Snap a LinkedIn job post and it extracts title, company, and location.
- An agent with memory works out what the message is and which tool to call. There are no commands or syntax to remember; the interface is "just say it."
- Tools it routes to: append rows to the right Google Sheets tab (to-dos, job leads, reading list, wedding planning), create Google Calendar events, draft Gmail replies, or search the web.
- Confirmation comes back on WhatsApp, so the loop closes in the same thread the thought arrived in.
Architecture decisions
The whole system is one importable n8n workflow: trigger, switch on message type, transcription and vision branches, agent node, and a fan of tool nodes. Three decisions carried it:
- Low-code on purpose. Swapping a tool or adding a new list is a node edit, not a deploy. Requirements change weekly here, so iteration speed beats code elegance.
- The agent decides, the tools constrain. The model chooses which tool to call, but each tool writes to a fixed, typed destination. Flexible understanding, rigid outputs.
- Structured rows, not notes. Everything lands as columns in the right tab, so the sheets stay queryable instead of becoming another pile to read.
Business impact
- Capture rate is the metric. When filing a task costs one WhatsApp message, in whatever form the thought arrived, everything gets filed. The sheets became trustworthy because they were finally complete.
- Build cost was an evening; run cost is pennies. Total cost of ownership is one person occasionally editing nodes. No repo, no pipeline, no maintenance burden to justify.
- The pattern is the pitch. This is the smallest honest demo of an agent plus tools plus existing systems of record, which is what intake automation, CRM hygiene, and ticket routing all reduce to. Proving it on a personal workflow is how you learn the failure modes before proposing it with a budget attached.
Risks & guardrails
- Drafts, not sends. The Gmail tool only drafts replies; a human hits send. Autonomy in processing, human control at the point of external action.
- Fixed tool destinations. A confused agent can file to the wrong list, but can't touch anything outside its fan of tools.
- Confirmation on every action closes the loop in-channel, so a mis-filed item gets caught in seconds rather than discovered weeks later.
Where it goes next
An n8n canvas screenshot and a WhatsApp exchange for this page, a weekly digest message summarizing what got filed, and retiring lists as life changes. The wedding-planning tab has a natural expiry date.