turn your notes into a comment on the right asana task

stop making your team hunt through email for the latest date. a bot finds the right asana task and puts a plain text update beside it.

by the dusk bot team · checked 12 november 2026 · how we made this

you get the news where the work lives, with the project confirmed before posting. comments count as sends and ask first by default. set a sending rule when every comment needs your review.

pixel art: a lime pixel bot and a yellow pixel bot beside the Asana mark on a white tile, two chat bubbles and a notebook, on a lilac hill in front of a calm sea with one small island, one saying "update on the task"

create task comment, in plain words

a comment keeps the news with the work. give the bot the task's project and the words to post. it can look through project tasks, open the match and add your update to its activity feed.

this field accepts plain text only. html, rich headings and styled links won't carry over. use short lines that still make sense without formatting.

a routine to copy

paste this into a chat with your bot

on fridays at 11, read this week's emails from people at @tallowmere.com that confirm a new delivery date.

- find the matching task in the mobile checkout project in asana
- write a plain text comment with the new date, who confirmed it and when
- show me each task and comment here; post only the ones i allow

never change a task's due date or owner. if no email qualifies, say so briefly. don't invent a date or confirmation.

when: fridays at 11:00
needs: gmail read only; asana read and write for task lookup and comments

what comes back looks like this (an example)

packaging samples
proposed comment: 'coralie at tallowmere confirmed delivery on 21 november in her email this week.'

ready to post after approval. due date and owner stay as they are.

good jobs for it

keep test evidence close. post the result beside the task your team will review.
record a delivery change. quote the supplier's new date without editing the task deadline.
close a design question. add the answer you approved to the task's discussion.
leave a useful handoff. say what finished and which question remains open.

before it runs

dusk bot counts Create task comment as a send: it reaches people or moves money, so it waits for your Allow (unless you set a daily amount, or the bot is on Full access with no sending rule, which lets it send up to 25 a day). a bot you allow only to read can never call it.

how to start

connect the two apps. give this bot gmail read only and asana read and write.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
try one update. open its task and activity feed before scheduling the friday run.

limits worth knowing

same title, wrong team. open the task in its project. the connected account needs access there too.
plain text means plain text. don't depend on html or rich formatting to carry the meaning.
keep the final word on comments. a daily sending allowance skips individual reviews.
sleep can cost you a run. a miss under 12 hours runs once when you return. older runs skip. dusk cloud runs on time.

the details it works from

input	required	what it is
`text`	yes	The plain text content of the comment to be posted on the task.
`task_id`	yes	The globally unique identifier (GID) of the Asana task to which the comment will be added.

from composio's catalog for Asana (action ASANA_CREATE_TASK_COMMENT, read 12 november 2026⁴). your bot fills these in from what you tell it.

try it in 2 minutes

name one task and its asana project
paste one confirmed delivery update
ask for the comment here first
open the task in its project, then allow the comment

mistakes people make

posting under a familiar title

open the project too. repeated task names are an easy way to tell the wrong team.

rewriting the deadline along with the comment

say "comment only; leave dates and owners alone". a delivery note is not a reschedule.

questions

can it post the comment without changing the deadline?

yes, the comment leaves task fields alone. allow only task lookups and comments if that is the whole job.

will bold text and formatted lists carry over?

no rich formatting here. ask for ordinary text and short lines. html and styled emphasis won't survive this field.

what if two asana tasks have the same title?

choose by project as well as title. ask the bot to show both matches before posting. you name the work; it finds the task.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: sending and approval settings
composio, Asana toolkit (catalog version 20261104_00), checked 12 november 2026

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].