an asana assistant for the work between tasks

what a bot can do in Asana

a task title rarely explains a delay. ask the bot to read the project, its task comments and the dependencies together. these actions let a review name the unfinished work instead of guessing from a due date.

composio, the connection service dusk bot uses for apps, lists 247 Asana actions (catalog version 20261104_00, read 12 november 2026⁴). dusk bot treats 118 of them as reads, 1 as sends and the other 128 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like create task comment: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Asana

1. open Connected apps in the sidebar.
2. pick Asana and sign in on Asana's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Asana.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

in Connected apps, allow the project bot to use asana. keep it read only for the first review. tell it the workspace and project you mean, especially if several projects share a name. an exact list of allowed actions can keep task creation available while leaving unrelated changes out of reach.

routines to copy

send one of these messages after naming your project. the result belongs in your dusk bot chat, where you can correct the interpretation before giving the bot permission to edit tasks.

every afternoon at 3, review the asana tasks in our launch project due tomorrow. inspect their subtasks and dependencies. list unfinished prerequisites and the person assigned to each, where recorded. keep all task dates unchanged.

every monday at 10, read the latest status update in the website project and compare it with its tasks. point out claims of completion that still have unfinished subtasks. cite the task names and separate missing information from contradictions.

every thursday at 2, find tasks assigned to the contractor i named in the design project. read the comments and list questions still awaiting our answer. group them by task. do not reassign work or post comments.

what it asks you first

read-only access prevents task creation, edits and section moves before a call reaches asana. if you later enable changes, write "ask me before you change anything" into the routine when you want to review them. do not assume a due-date edit or reassignment has a separate approval card.

sends through connected apps ask first by default, unless you set a daily sending allowance. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. that sending rule is separate from permission to change project records. use a small allowed action list for a bot whose only writing job is creating agreed tasks.

what it cannot do

• work on a project outside the access available to its connected account. a similarly named project is not a reason to guess; give the bot the exact project.
• create tasks or correct assignments while the asana connection for that bot is read only. the review routines above deliberately leave those records alone.
• run a scheduled handoff check on a sleeping desktop. local routines pause when your computer sleeps or dusk bot closes; dusk cloud can keep them running.

give a blocked task some context

tell the bot what counts as blocked for your team. an unfinished dependency is useful evidence; a quiet comment thread is a question to investigate. ask it to show both the evidence and what it could not find.

if delivery also lives in jira, connect that app separately. teams working mainly in linear can start with its issue review instead.

keep the review small

choose a project and a decision: can we hand this off, what needs an answer, or does the status note match the tasks? asking for everything in a workspace makes it harder to notice a wrong assumption. pause or edit the schedule from Automations after the first few runs.