dusk bot
integrationsadd database row

dusk botintegrationsnotion

turn a clear request into a notion database row

get the approved purchase out of your notes and into the tracker. a bot adds a notion database row with table properties and a short page body.

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

missing fields can stay empty. share the database with the connection first, and use a database with one data source. put any approval step in the request.

pixel art: a green pixel bot, a lime pixel bot and a purple pixel bot beside the Notion mark on a white tile, a notebook and a big button, on a sandy path in front of white cliffs with a waterfall, one saying "add the approved entry"

what it does

put the headline in the table and the detail inside the row. properties fill the columns; content blocks hold the longer note. paste the database link and have the bot read its columns first.

keep entries short. long text can lose its ending, and extra blocks arrive after the page exists. open the body to see the whole note. this inserts a new row rather than updating an old one.

when you would use it

  • record a confirmed equipment purchase in your purchasing database
  • add an accepted research proposal with its short brief inside
  • log a workshop booking after the date and organiser agree
  • save an idea with its source and leave undecided fields empty

try it

paste this into a chat with your bot

every thursday at 12:35, read new approval files added this week to the 'approved purchases' google drive folder for thistledown theatre. look for existing entries in the linked notion purchasing database. show proposed rows here with the source file and matching columns. ask me before you change anything. create only the rows i confirm, with short source notes. never guess costs or update old rows. if an insert result is uncertain, look for the row before trying again.
when
thursdays at 12:35
needs
google drive read only; notion read and write; a single-source database shared with the connection

what comes back looks like this (an example)

thistledown theatre purchase preview
item: portable lectern
source: approved purchases / lectern-approval.pdf
cost: missing, left empty
confirm this preview to create the row.

set it up

  1. connect notion and share the intended database with the connection
  2. allow read and write, limited to inspection and insertion
  3. match one short entry to the actual columns before inserting
  4. open the saved row and its body; pause if anything went missing

what it needs from you

inputrequiredwhat it is
database_idyesIdentifier (UUID) of the Notion database where the new page (row) will be inserted.
iconnoEmoji to be used as the page icon.
covernoURL of an external image to set as the page cover.
propertiesno$52
child_blocksnoA list of `NotionRichText` objects defining content blocks (e.g., paragraphs, headings, media) to append to the new page's body.

from composio's catalog for Notion (action NOTION_INSERT_ROW_DATABASE, read 12 november 20264). your bot fills these in from what you tell it.

how dusk bot handles it

dusk bot counts Insert row database 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.

where it stops

  • choose a database with one data source. this action cannot insert into a multi-source database.
  • a row can exist before its whole body arrives. inspect long notes and extra blocks.
  • inserts do not ask first by default. put the review instruction in your message.

try it in 2 minutes

  1. share one notion database with the connection
  2. ask the bot to read its columns
  3. preview one short row with missing fields empty
  4. confirm, then inspect the row and body

mistakes people make

retrying because the body looks unfinished

look for the row first. its body can still be arriving.

feeding the routine approvals buried in chat

point it at new approval files in a connected folder.

questions

is a database row different from a notion page?

the row is a page inside the database. its properties fill the table. its content blocks form the page body.

will it replace a row with the same title?

each insert adds a fresh row. look for an existing entry before retrying an uncertain result, even when the title is the same.

sources

  1. dusk bot docs: files and apps
  2. dusk bot docs: routines
  3. dusk bot docs: a bot's computer
  4. composio, Notion toolkit (catalog version 20261101_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].