What the agent does
This is for a nonprofit whose development team tracks grant applications and funder reports in Asana: one project called "Grants", one task per application or report with its due date, and subtasks for the pieces each funder asks for, such as the narrative, the budget, the audited financials, letters of support and the board list. The development director needs a Monday view of what is due in the next six weeks and what is still missing, without opening every task. The run names one connection, asana, Rush's own Asana sign-in, which reaches Asana's MCP server at https://mcp.asana.com/v2/mcp as the director.
The agent finds the project with Asana's search_objects tool and lists its tasks with get_tasks, which works on every Asana plan, unlike search_tasks, which Asana documents as Premium only. For each incomplete task due in the window it calls get_task, which returns the task's details with its comments and subtasks, and reads the custom fields the team uses, such as the funder and the amount requested, exactly as they are set.
For each application or report it works out what is left: the subtasks not completed, who each is assigned to and its own due date, and any comment from the last two weeks that says a piece is waiting on someone ("finance says audit letter by the 20th"). It flags a subtask with no assignee, a subtask due after its parent, and a parent due in the next 14 days with more than half its subtasks open. It reads get_task_stories only for tasks whose due date moved, to report when it changed and who changed it.
It writes grant-deadlines.md: due in the next 14 days first, then the rest of the six weeks, each with the funder, the due date, what is left, owners and the flags. Then it posts one status update to the Grants project with create_project_status_update, the count due in 14 days and the items flagged, so the whole team sees it in Asana. It changes no task, due date or assignee.
Start it with one API call
POST https://api.phoenix.so/o/{org}/sessions with this body:
{
"agent": "claude",
"input": "Use the Asana connection. Find the project named 'Grants'. With get_tasks, list its incomplete tasks due between 2026-11-16 and 2026-12-28. For each, read it with get_task (details, comments, subtasks) and its funder and amount custom fields as set. For each task, list incomplete subtasks with assignee and due date, and quote any comment from the last 14 days saying a piece is waiting on someone. Flag: subtasks with no assignee; subtasks due after their parent; parents due by 2026-11-30 with more than half their subtasks open. For tasks whose due date changed, read get_task_stories and say when and by whom. Write grant-deadlines.md, soonest first. Then post one project status update on Grants with the count due by 2026-11-30 and the flagged items. Do not edit, complete, reassign or comment on any task.",
"connections": [
"asana"
]
}- Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
- Send the request. POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
- Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.
What comes back
The session returns grant-deadlines.md as an artifact and its text in result, and the team sees a status update on the Grants project in Asana. The director reads the file before the Monday meeting and goes straight to the applications due soon with pieces still open, and the people named as owners see their items without anyone sending a list.
What the director checks: amounts and funders as the agent read them from custom fields, which are only as accurate as the team keeps them; any piece the agent marked as waiting on someone based on a comment, which is quoted; and work that happens outside Asana, such as a budget drafted in a spreadsheet nobody linked, which the agent cannot see. The transcript shows each Asana tool call and the task it read.
Run it on every Monday morning
In the console, a Project automation with a schedule trigger, cron 0 8 * * 1 in the nonprofit's timezone, runs a saved agent that names asana and keeps the project name, the flags and the six-week window in its instructions; the automation's prompt only says to run this week's check.
Before a board meeting or a funder deadline crunch, the director can run the same saved agent from the console with a different window, and it writes a new file without touching the Monday run's.
The use case this job follows, with its automation and trigger: Produce a report or file, no repo.
Why run it on Rush?
A grant tracker in Asana already has the dates; what a person adds each Monday is reading the subtasks and comments to see what is actually missing and who is waiting on whom. Asana's own views show dates and assignees but not "the audit letter is coming from finance on the 20th". The agent reads those comments and quotes them, so the director can check its reasons in a glance.
The Asana sign-in stays in Rush's connection, not in a personal access token kept by whoever set up a script. Each Monday's run has its own computer and its own record of what it read and the update it posted, and the session lists what its model calls cost.
Frequently asked questions
Will the agent write the grant applications?
Not in this run. It tracks deadlines and missing pieces. Drafting a narrative is a separate job, and what goes to a funder is the development team's to write and approve.
Does it need Asana Premium?
No. It uses get_tasks, which Asana's MCP documentation lists for non-Premium workspaces, and reads each task with get_task. Only search_tasks is documented as Premium only, and the prompt does not use it.
Can it see projects the director cannot?
No. The sign-in is the director's, so the agent sees what the director sees in Asana, and the prompt keeps it to the Grants project.
Can we turn off the status update?
Yes. Remove the last step from the prompt and the run only writes the file. With it, the update is the one thing the run writes in Asana.
More Asana jobs
More jobs like this: Produce a report or file, no repo
- Track Which Clients Still Owe Documents From the Firm's Outlook Inbox (Outlook)
- Which Clients' Month-End Close Is Behind? A Bookkeeping Firm's ClickUp Report (ClickUp)
- Triage Customers' Jam Bug Recordings Into Reproducible Reports (Jam)
- How Does a Property Manager Triage Each Morning's Maintenance Requests in Airtable? (Airtable)