Asana Task Triage Agent

Asana notifies an integration that a resource changed, not what the task actually says, which is why so many Asana bots triage a stub and get it wrong. This agent fetches the task and reads its real fields first, then places it in the right section, assigns whoever owns that kind of work, and leaves one comment listing what is still missing. Requests get placed on the day they arrive instead of ageing quietly at the bottom of the project.

What people use it for

• Judged on real fields - Because the change event carries an id and little else, the agent pulls the full task first. Notes, due date, custom fields, and current section all inform the call, so triage is not guesswork built on a title.
• Sections stop being a graveyard - New work is moved into the section your rules point at as it arrives, which keeps the untriaged pile from becoming the place requests go to be forgotten.
• The owner comes from the map - Assignment follows the kind of work rather than whoever was tagged in the description, and genuinely ambiguous tasks stay unassigned with the deciding question written out.
• One comment, never a checklist - The reply asks only for the pieces your rules require and this task lacks, such as the deliverable or a link to the brief, which reads as help rather than a form to fill in.

Before you fork

Asana already sends us the event. Why does the agent fetch the task again?

Because an Asana change event tells you a resource changed and which one, not what it contains. Triaging from that alone means routing on a fragment, so the agent always pulls the current task and reads the fields as they stand right now, which also means edits made between the event and the run are handled correctly.

Won't it re triage tasks every time somebody edits them?

No. It acts on tasks that are new and untriaged. A task already sitting in a section with an owner on it is treated as settled and the run stops without a write, which is what happens on the vast majority of change events in an active project.

What is it allowed to do to a task, and what does it need from us?

It sets the section, sets the assignee, and adds a single comment. Completing tasks, editing names, notes, or due dates sit outside its reach entirely. You connect an Asana credential with access to the project plus a Slack channel for urgent work, and you write the triage rules and ownership map in your own words.