add new records to the end of a google sheets table

get this week’s records into the sheet without replacing last week’s. the bot adds rows after your google sheets table.

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

paste the link, name the tab and give the column order. the range helps it find the table’s end; it does not choose an exact empty cell. ask for a row preview and a pause before it writes.

pixel art: a mint pixel bot and a coral pixel bot beside the Google Sheets mark on a white tile, a chart on an easel and a notebook, on a lilac hill in front of sand dunes by the sea, one saying "new records below"

what it does

use append for a log that keeps growing. each new entry gets a row after the existing table. the bot reads tab names and column headings before writing.

name the tab exactly and compare the proposed column order with its headings. “attendance” and “session log” can be different places in the same file.

say whether codes should stay literal text or whether sheets should interpret values such as dates.

when you would use it

finish the workshop register. add the attendance entries from your session records.
extend the loan log. append equipment loans after approval.
keep registrations together. add visitors in the register’s column order.
record fresh inspections. add completed checks without replacing older ones.

try it

paste this into a chat with your bot

every saturday at 12, read attendance files added this week to the pottery attendance folder in google drive. use only files whose names end in final. open the foxmere studio attendance spreadsheet, get its actual tab names and read the session log headers. compare existing rows to avoid adding the same session batch again. arrange new rows as session date, attendee name and attendance status. keep names exactly as written. show the rows and destination here. ask me before you change anything. after approval, append the rows and report where they landed. never change old attendance rows. ask if a batch looks duplicated.

when: saturdays at 12:00
needs: google drive read only for attendance files; google sheets read and write for the session log

what comes back looks like this (an example)

attendance append proposal

foxmere studio, session log
session date | attendee name | attendance status
14 november 2026 | thalia | attended
14 november 2026 | rafael | attended

ready to add below the existing sessions after your review.

set it up

share the right sheet. connect sheets and paste the attendance file’s link.
allow a narrow write. permit reading tab names, reading the table and appending rows.
line up one row. compare its values with the column headings. say which codes must stay literal text.
open the saved row. its date, name and status should sit under the right headings. pause the routine between workshop seasons.

what it needs from you

input	required	what it is
`range`	yes	A1 notation range used to locate a logical table.
`values`	yes	2D array of values to append.
`spreadsheetId`	yes	The spreadsheet ID (typically 44 characters containing letters, numbers, hyphens, and underscores).
`valueInputOption`	yes	How the input data should be interpreted.
`majorDimension`	no	How to interpret the 2D values array.
`insertDataOption`	no	How the input data should be inserted.

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

how dusk bot handles it

dusk bot counts Append Values to Spreadsheet as a change: it alters something in Google Sheets, and the sending setting does not cover it. a bot you allow only to read can never call it.

the permissions Google Sheets asks for to run it: spreadsheets, drive, drive.file.

where it stops

the table decides the next row. an unexpected gap or table boundary can change where entries land.
read back what matters. ask to see the saved rows instead of assuming the preview matches them.
retrying can duplicate records. append adds; it does not match and repair existing entries. look for the batch in the table before another attempt.

try it in 2 minutes

paste the sheet link and tab name
ask the bot to read the headings
preview one new record in column order
append after review and read the saved row

mistakes people make

retrying after an unclear result

read the table first. the first attempt may already have added the rows.

guessing the tab name

have the bot list the real tabs before choosing the destination.

questions

can i choose the exact row number it writes to?

use a cell update for that. append finds the table’s end inside the chosen range and writes after it.

does it correct a record that is already there?

no. it adds rows. fixing an existing entry needs a different action.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: a bot's computer
composio, Google Sheets 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].