Today’s tool is the one my agents write to more than any other: the Asana API. Every scheduled job in my fleet ends by filing a task. That part works perfectly. The trouble is what happens after.
What my agents use it for
Asana is the paper trail for my agent fleet. When a job finishes, it does one of three things:
- Logs the run in a Done section: what it did, the IDs, the links.
- Files a review task in a “Drafts (Awaiting Approval)” section after it publishes something, so I can check it.
- Flags a problem in the Inbox when it gets stuck and needs me.
The API is easy for an agent to drive. It’s one POST to /tasks with a name, notes and a project, then one POST to put it in a section. The rate limits are generous for this kind of work: 150 requests a minute on a free workspace, 1,500 on a paid one, with up to 15 writes in flight at a time.
The receipt
I pulled every task in the project through the API this morning (19 November 2026).
- 2,158 tasks since the project started on 12 June. 994 are still open.
- The Done section works: 331 run logs, all but 2 closed.
- “Drafts (Awaiting Approval)” has 269 tasks. 265 are still open. The oldest is from 15 June. None has an assignee, and only 1 has a due date.
- The 4 that were closed were closed in the same minute they were created. A reviewer didn’t close them. The agent that filed them did.
- The Inbox has 686 open tasks. 147 are daily watchdog reports.
There’s one more catch. Every one of those 2,158 tasks says it was created by Jon Jones, because my agents use my API token. Asana can’t tell me which tasks I typed and which a script filed.
The Inbox tasks that did get closed were nearly all blockers with one clear ask, like an expired social media token or a bounce-rate alarm on my outreach. A clear problem got a fix. A pile of “please review” never got a single real close.

⚡ GET THE AI EDGE
Weekly AI tips that actually save you time and money. No fluff, no hype — just what works.
The lesson: a task nobody owns is a log entry
An approval queue only works if someone is on the other end of it. With no assignee and no due date, the task doesn’t land in anyone’s My Tasks list, and it has no deadline to go overdue. It just sits in a section and looks responsible.
It’s the same lesson as my Telegram alerts count, where 66 bad runs produced 1 alert. Writing something down is not the same as telling someone.
How to set it up so it doesn’t pile up
- Split logs from requests. If nobody needs to act, create the task with
"completed": true. It’s still searchable and it never adds to an open count. - Every request gets an owner, a date and one question. Set
assigneeanddue_on, and put the question in the title (“Approve or edit by Friday?”), not halfway down the notes. - Give your agents their own identity. A separate Asana user or service account for the bots means “created by” tells you something. Mine doesn’t yet.
- Count the queue every week. One GET per section with
opt_fields=completedgives you the open count. If it only goes up, the queue isn’t being worked. Or let a second agent check the first one’s work so fewer things need you at all.
Honest status: those 265 are still open as I write this, and this post will add one more when its review task gets filed. Clearing them and changing how my agents file them is on my list. It isn’t done yet.
The takeaway: the Asana API makes it effortless for an agent to ask for your attention. Make sure every ask has a name and a date on it, or it’s just a diary.
Want your agents’ handoffs set up so the things that need you actually reach you? Book a strategy session.

📥 FREE: THE AI PLAYBOOK
The exact tools and workflows I use to run a one-person agency. 25 years of marketing experience distilled into an actionable guide. Yours free.
