dusk bot
integrationsgoogle tasks

dusk botintegrations

see which google tasks still need a decision

decide what to do with the overdue tasks you keep carrying forward. a google tasks bot in dusk can read across your lists and bring back each task with its notes and original list.

by the dusk bot team · checked · how we made this

ask for a shortlist to work through today. leave every due date in place until you choose what moves.

pixel art: an indigo cat bot and a cyan pixel bot beside a tile saying Google Tasks and a shopping bag, on a grassy meadow in front of chalk cliffs by the sea, one saying "what can wait"

what a bot can do in Google Tasks

keep the list name beside every task. two tasks called “pick up keys” may belong to different jobs. the cross-list action returns the list id and title. the single-task lookup uses both ids to reopen exactly the task you mean.

actiondusk bot treats it aswhat you would use it for
List task listsreadfind the work and personal lists even when their titles look alike
List All Tasks Across All Listsreadcollect open work across lists and keep each task’s source
List Tasksreadfilter one list by due dates or completion dates
Get Taskreadrefresh a task before relying on its latest notes
Patch Taskchangechange just the due date you agreed to move
Move Taskchangemove an errand to another list or position it under a parent
Insert Taskchangeadd a new follow-up to the intended list

composio, the connection service behind dusk bot's apps, lists 18 Google Tasks actions (version 20261116_00, read 20 november 20263). dusk bot treats 5 as reads, 0 as sends and 13 as changes.

only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, and waits for your Allow unless you set a daily amount.

connect Google Tasks

  1. open Connected apps in the sidebar.
  2. pick Google Tasks and sign in on Google Tasks'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 Google Tasks.
  4. ask in plain words. reading and drafting happen freely; sending asks you first.

connect the google account that holds your lists. let your planning bot read google tasks. ask it to show your list titles, then name the ones that belong in the daily review. keep a client list out of the errands routine if the two share a name.

routines to copy

choose the moment you usually reopen the list. these messages build a plan from the tasks you already wrote. change the list names in the bot’s job to match yours.

decide on overdue work

each weekday at 8, read incomplete tasks due before today from my work lists. group them by original due date. include the task notes if they name someone waiting. give me the three oldest first in this chat. leave every due date alone.

weekdays at 8 am · overdue decisions with the original deadlines intact

errands to take along

every saturday at 10, read my home and errands lists. find unfinished tasks whose title or notes name a pickup, return or drop-off. group them by the place actually named. put tasks without a place together here. do not move them between lists.

saturdays at 10 am · one errand list for the trip, grouped by place

completed work for my timesheet

every friday at 4, list tasks i completed on my client lists since monday. include completed and hidden tasks. group the titles by client list and completion day here. copy any duration i wrote in the notes. leave hours blank everywhere else.

fridays at 4 pm · a timesheet aid with only the hours you recorded

what it asks you first

review a proposed move before handing over the task list. moving tasks, changing dates and inserting tasks are writes. they can run without asking. keep planning read only. for an editing routine, write “ask me before you change anything” and have it name the task and destination.

what it cannot do

  • store a due hour with the insert action. google tasks keeps the date and discards the time. a run at ten does not give the task a ten o’clock due time.
  • open a task by its id alone. the single-task action also requires its list id.
  • assume the cross-list result covers everything. it defaults to 1,000 tasks and indicates when it cuts off results. narrow the lists or adjust the limit before calling the review complete.

when to keep the pencil yourself

change a single obvious date in google tasks. a chat adds a step when you already know the task and its new deadline. use dusk when the next decision depends on notes and due dates spread across several lists.

what it looks like

a fictional example.

before

frank meyer has “return sample” on his home list and “return lamp” on his errands list. only the lamp task names a shop.

after the bot

trip list: take the lamp to the lighting shop. the sample still needs a destination. both tasks keep their original lists and dates.

an illustration with made-up names and numbers.

questions

can a google tasks ai assistant reorder my list?

yes, with the move action enabled. give the destination list or the sibling it should follow. ask for a proposed order in chat first.

will repeating a request to add a task create a duplicate?

it can. if the first insert gave an unclear result, have the bot read the destination list. confirm whether the task already exists before trying again.

sources

  1. dusk bot docs: files and apps
  2. dusk bot docs: routines
  3. composio, Google Tasks toolkit (catalog version 20261116_00), checked 20 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].