Overview
A client-mode connector for a curated work-management / documentation slice of the Notion REST API:
Default
BASE_ADDRESS is https://api.notion.com. Topics use devops/notion/<object>/<verb>.
Every request must include Notion-Version: 2022-06-28. This template pins that version so catalog POST /v1/databases/{id}/query remains valid; Notion deprecates that path under API versions 2025-09-03 and later (databases → data sources).
Auth is Bearer integration secret, OAuth 2.0 access token, or PAT (
Authorization: Bearer …). Prefer Hub secret NOTION_API_TOKEN (aliases NOTION_TOKEN, NOTION_INTEGRATION_TOKEN, NOTION_ACCESS_TOKEN). Status remains blocked until an authenticated live smoke succeeds. Share target databases/pages with the integration or Notion returns HTTP 404.Basic Syntax
Events
Auth
- Create an internal integration (or use OAuth / PAT) and copy the secret.
- Set connector
BASE_ADDRESStohttps://api.notion.com. - Pass
access_tokenon MQTT JSON payloads so the Bearer header resolves. For path params, also passpage_id/database_id. - Store secrets in Hub /
GET SECRET "NOTION_API_TOKEN"(aliasesNOTION_TOKEN,NOTION_INTEGRATION_TOKEN,NOTION_ACCESS_TOKEN). Never commit real credentials. - Share databases/pages with the connection via Notion Add connections.
- Successful smoke:
GET /v1/users/mewithNotion-Version: 2022-06-28→ HTTP 200 withid. Invalid tokens → HTTP 401.
Example payloads
getUserMe (smoke):Deploy notes
- Deploy
NotionRestApi.lotonly (noADD METADATA). - Hub catalog metadata lives in
hub-metadata.lot(WITH STATUS "beta", icon, doclink). - Docs: https://docs.coreflux.org/latest/lot-language/routes/rest-api-apps/notion

