How it works
Three steps. Confirm is the only thing that ever writes.
Notion's Repeat writes one row, on the day it's due. Cadence writes the next ten — after you confirm.
Step 1
Authorize Cadence for the databases you choose. Page bodies are never read.
Nothing is created yet.
Live preview. Writes nothing.
Step 2
See weekday, date, and title for each occurrence.
Live preview. Writes nothing.
Write 10 rows to Notion
Preview stays read-only until you confirm.
Step 3
Confirm is the only thing that ever writes.
The modal lists every row before Cadence creates it.
Curious what you’re authorizing? See exactly what Cadence can access before you connect.
Under the hood
reserved
A reserved slot is held per rule and date before anything is written — so Confirm cannot double-create.
cadence_ref
Every row Cadence writes carries a cadence_ref stamp. Verification uses Cadence-owned properties only.
retries
Retries never delete your Notion rows. Failed creates stay reserved until they succeed or you intervene.
2.5 req/s
Cadence stays polite to Notion’s API — about 2.5 requests per second, not a burst flood.
Sourced from the same claims as Privacy. No new product promises here.
Preview is free. Confirm is yours.