Asana Task Triage Agent with Claude Code
Asana tells an integration that a resource changed and which one, and nothing whatsoever about what it says. The most important line in the template is therefore an act of patience: fetch the task, read the real fields, and only then decide whether this is new work at all. Claude Code plans before it acts, so the fetch then judge order holds rather than collapsing into a guess from the event payload.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Redraw the pricing page for the Q3 brand update
Eassigned to Emeka Balogun
The pricing page needs redrawing in the new brand by 5 August so it goes out with the Q3 announcement. Figma file and the approved palette are linked in the description. Copy is final and Leena has signed it off.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Asana
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Triage rules
Your triage rules - which section each kind of task belongs in, what a task has to contain before work can start on it, and what makes something urgent enough to interrupt a person.
Team map
Each kind of work matched to the Asana teammate who owns it, and the fallback owner for tasks that fit none of them.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
Fetch first, every time
Name, notes, due date, current section and custom fields are all read before a section is chosen. Skipping that step is how Asana bots end up routing on a fragment of a task.
Stops on settled tasks
A task already sitting in a section with an owner ends the run with no write at all. Obeying a rule that says do nothing is a discipline, and this harness holds it.
Before you fork
Who ends up looking after this once it is live?
Whoever owns the project, not an engineer. Two things need maintaining, the triage rules and the ownership map, both written in plain sentences and both edited where you first set them. The Asana credential and the Slack channel are configured once at the start and then forgotten.
Run it with a different agent
Put Asana Task Triage Agent to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.