Notion
Database query is a POST, so a stored secret cannot be sent. Use a sheet or push.
What you can track
Counts and sums from a Notion database, after a script or automation writes them to the sheet or the push address.
Credential
None in tlly for those two paths.
Notion’s own query is POST /v1/databases/{database_id}/query with Authorization: Bearer and header Notion-Version. The page checked says that route is deprecated as of version 2025-09-03 and points at a newer “query a data source” API. This playbook did not fetch the new page, so it does not name that path. Both are POSTs. tlly will not send a stored secret on them.
The connection needs read content capability, and the database must be shared with the connection, or Notion answers 404. That is for a script you run, not for a tlly job.
Where to get it
Notion → Settings → Connections → Develop or manage integrations → create an internal integration, copy the token, and share the database with it (••• → Add connections). Then have that script push numbers.
tlly job
Sheet or push. Not api.notion.com.
Gotchas
- A 404 from Notion often means the database was not shared with the integration, not that the id is wrong.
- Formula and rollup values are limited (the query page warns that relations over 25 references are partial). Prefer a number property the script already reduced to one value.
Alert ideas
Red when the pushed count crosses the ceiling the user names.
Verification
Checked 2026-10-26: the database query page is POST, deprecated as of 2025-09-03, requires the database to be shared, and requires read content capability. The replacement endpoint was not fetched (unverified). The Notion-Version header is the usual requirement and was not quoted from a fresh authentication page in this pass; do not invent a version string.