dusk botask for the notion records that match your conditions
stop scanning the whole tracker for a handful of rows. name the status, date or other condition you need. the bot asks notion for matches and sorts the results.
give the database's own link. dusk counts this query as a change, so allow read and write for this exact action and its lookups.
what it does
get next week's confirmed bookings in one dated list. paste the database's own link, or ask the bot to find it. a page containing a tracker is a different thing.
the bot reads the field names and types, applies your conditions and sorts by session date. for a large list, tell it to keep going until notion has no more matches.
when you would use it
- list confirmed studio bookings in the next fortnight
- find equipment loans still out after their due date
- sort approved grant applications by decision date
- pull records from an archived year for a historical report
try it
paste this into a chat with your bot
at 17:05 each sunday, read the fields in my linked studio bookings database. find confirmed bookings with session dates in the coming week. sort by session date and keep going until notion has no more matches. put the dated list here. report missing dates or failed reads without guessing. never edit bookings, assign owners or change the database.- when
- sundays at 17:05
- needs
- notion with read and write, limited to the query and its database lookups
what comes back looks like this (an example)
confirmed studio bookings
- monday: emma, portrait room
- thursday: noah, recording booth
sorted by session date. the week's matches are all here.set it up
- connect notion. allow read and write for this query and the database lookups it needs.
- paste the database link. ask the bot to read field names and types first.
- try a filter with matches you already know. compare their dates and order.
- schedule the weekly query. Edit shows its next run. leave row-edit actions out.
what it needs from you
| input | required | what it is |
|---|---|---|
database_id | yes | The UUID of the Notion database to query (32 character hex string, with hyphens or without). |
sorts | no | List of sort criteria in order of precedence. |
filter | no | $53 |
page_size | no | Maximum number of items to return (1–100). |
start_cursor | no | Cursor from a prior response's `next_cursor` for fetching the next page. |
composio_execution_message | no | Internal message about any automatic conversions made during execution. |
from composio's catalog for Notion (action NOTION_QUERY_DATABASE_WITH_FILTER, read 12 november 20264). your bot fills these in from what you tell it.
how dusk bot handles it
dusk bot counts Query database with filter as a change: it alters something in Notion, and the sending setting does not cover it. a bot you allow only to read can never call it.
the permissions Notion asks for to run it: read_content.
where it stops
- use the database link. the surrounding page's link can point the query at the wrong thing.
- 100 rows is one batch. ask the bot to keep reading until it has every match.
- sort by the date you plan around. created date and your booking-date column can give very different lists.
- allow this query without handing over row edits. dusk classes it as a write, so read only blocks it. limit access to the query and its lookups.
try it in 2 minutes
- copy the database's own link into your request
- ask for confirmed rows due next week, sorted by the due-date column
- compare the matches with a filter you know
mistakes people make
pasting the page around an inline database
open the database and copy its own link.
sorting by row creation instead of the booking date
name the date column you actually plan around.
questions
why does a database query need read and write access?
dusk counts this action as a change. narrow the allowance to the query and its database lookups. you do not need general page edits.
can it combine a status with a date condition?
yes. the bot reads the real field names and types, then sends the combined conditions to notion.
does sorting the query rearrange my notion database?
no. sorting controls the returned list. it does not rearrange the database itself.
sources
read next
match a notion record before adding another rowmatch the reference before writing the record.
a notion bot that keeps the next step easy to findclearer notes, with a smaller edit scope.
add a batch of notes to an existing notion pageadd the notes where they belong.
leave a useful notion comment where it belongsa review note in its intended discussion.
give new notion notes a proper homenew notes, under the parent you chose.
turn a clear request into a notion database rowyour notes, in the right database fields.
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].