find the gmail drafts you have left unfinished

find the reply you meant to finish last week. a bot lists saved gmail drafts with recipients, subjects and full text, using read access alone.

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

ask what each draft still needs and get a useful to-do list back. gmail returns drafts without a fixed order, in batches. new drafts can take time to appear, so let the bot finish the list.

pixel art: a purple cat bot and a yellow pixel bot beside the Gmail mark on a white tile, a mailbox with a letter and a pair of binoculars, on a lemon field in front of chalk cliffs by the sea, one saying "still in drafts"

what it does

find the half-written email before it becomes a missed reply. full draft details let the bot see who it's for and what remains unfinished. a subject alone rarely tells the whole story.

gmail returns long lists in batches without sorting them by date. the bot needs to keep reading until there are no more. an incomplete search should say what it missed.

when you would use it

recover a forgotten follow-up. find the unfinished grant reviewer email without opening every draft.
see what you might clear. collect recipients and subjects before cleaning the folder yourself.
check a lost compose window. look for the saved proposal before writing it again.

try it

paste this into a chat with your bot

on mondays at 2, read all my gmail drafts with full details. keep fetching batches until the list ends.

show a checklist here for drafts addressed to pebblewake arts. include recipient, subject and what looks unfinished. mark anything you can't tell as unknown. say if an error leaves the list incomplete. never edit, delete or send a draft.

when: mondays at 14:00
needs: gmail read only, including full draft details

what comes back looks like this (an example)

pebblewake arts drafts
- marina: workshop proposal; closing paragraph unfinished.
- jun: materials list; body mentions an attachment to confirm.

end of draft list reached.

set it up

start with a reader. give the bot gmail read only in connected apps.
ask for the whole draft. recipients and bodies help distinguish two emails with similar subjects.
try one checklist. inspect it before scheduling. use edit for timing and pause to stop future runs.

what it needs from you

input	required	what it is
`verbose`	no	If true, fetches full draft details including subject, sender, recipient, body, and timestamp.
`page_token`	no	Token from a previous response to retrieve a specific page of drafts.
`max_results`	no	Maximum number of drafts to return per page.

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

how dusk bot handles it

dusk bot counts List Drafts as a read: it looks and changes nothing. a bot you allow only to read can use it.

the permissions Gmail asks for to run it: https://mail.google.com/, gmail.compose, gmail.modify, gmail.readonly.

where it stops

give a fresh draft time to appear. a short delay after saving is normal for this listing.
get the full folder, not its first batch. the bot should say where an error stopped it.

try it in 2 minutes

give the bot gmail read only
ask for all drafts with full details
pick a recipient or organisation to focus on
open one result in gmail and read its full text

mistakes people make

assuming the first draft is the newest

the list has no guaranteed order. ask for the details rather than trusting position.

retrying a fresh save over and over

wait, then ask again. fast repeated requests can make the list harder to retrieve.

questions

can it list draft bodies as well as subjects?

yes, ask for full details. the bot can read the draft text as well as its subject.

why is the draft i just created missing?

the listing can lag behind a save. wait before asking again. rapid repeat requests can hit gmail rate limits.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: computer permissions
composio, Gmail toolkit (catalog version 20261105_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].