dusk botask what an asana task actually says
start your shift knowing who owns the work and when it's due. name the asana task and project. a bot reads its owner, due date and instructions into a short brief.
ask for those details by name; the default view can leave them out. your account controls which tasks it can open. comments need their own lookup.
get a task, in plain words
chase the right person with the current instructions in hand. the bot finds the task in the project's list, then opens it. ask for owner, due date and notes by name.
it returns the supported details you request. add a separate read of comments when you need the discussion behind the task.
a routine to copy
paste this into a chat with your bot
every weekday at 8:30, read the dispatch instructions task in the warehouse operations project in asana. ask for its current notes, owner and due date. give me a short shift brief here. flag missing details. never edit the task or mark it complete. never treat a blank date as today's deadline.- when
- weekdays at 8:30
- needs
- asana connected with read only access for this bot
what comes back looks like this (an example)
dispatch instructions
owner: farah. due: 19 november.
pack the fernwell order separately. check the delivery address before labelling.
collection time: missing.good jobs for it
- start your shift with the current instructions. read the task from your phone.
- find the owner before chasing an update. don't guess from an old planning note.
- settle a date mismatch. compare the task's deadline with your planning notes.
- turn instructions into a checklist. keep the original notes untouched.
before it runs
dusk bot counts Get a task as a read: it looks and changes nothing. a bot you allow only to read can use it.
the permissions Asana asks for to run it: tasks:read.
how to start
- connect asana in connected apps. give this bot read only access.
- name the project and task. ask it to show the match first.
- ask for notes, owner and due date. tell it to flag blanks.
- read the first shift brief. use edit on the routine card to change it.
limits worth knowing
- your account sets the boundary. the bot cannot open a task you cannot read.
- put the details you need in the request. owner, due date and notes can be absent from the short view.
- notes aren't the discussion. ask for task comments and history as a separate read.
the details it works from
| input | required | what it is |
|---|---|---|
task_gid | yes | Globally unique identifier (GID) of the task. |
opt_fields | no | Array of field names to include in the response for more detailed data beyond the default compact representation. |
opt_pretty | no | If true, formats JSON response with indentation for readability; for debugging, as it increases response size/time. |
from composio's catalog for Asana (action ASANA_GET_A_TASK, read 12 november 20263). your bot fills these in from what you tell it.
try it in 2 minutes
- connect asana as read only
- name one project and task
- ask for its owner, due date and notes
- open the task and compare the answer
before you rely on the brief
- the task sits in the right project
- the bot asked for owner, date and notes
- missing details stay visibly missing
- comments have their own read when needed
mistakes people make
asking 'what's happening with dispatch?'
give the project and task title. broad questions invite the wrong match.
treating a blank deadline as overdue
ask it to say 'no due date', then ask the owner.
questions
can it read a task from just its name?
yes, with the project name too. the bot searches that project's task list, then opens the match. repeated titles need a closer look before it answers.
why did the bot miss the owner or due date?
ask for them by name. they might not come back in the short view. they might also be blank. ask the bot to tell you which happened.
will reading the task mark it complete?
no. this action only reads. read only access also blocks the bot from editing or completing tasks.
sources
read next
turn your notes into a comment on the right asana taskyour update beside the work it describes.
an asana assistant for the work between tasksfind the work holding up the handoff.
claude connectors: connect the job you actually needpick a task before you connect an app.
claude skills for people who do not write codea reusable method, with its materials.
an airtable assistant that learns the table before writingread the fields before filling the rows.
a canva bot for finding assets and preparing exportsfind the design. check the export.
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].