Repository navigation
Fetch authenticated Notion page content #85
Description
Context
This proposed #82 connector would have made Notion page text available in the catalog. It is closed as not planned because the project is not pursuing Notion; the criteria below preserve the canceled proposal and are not active work.
Acceptance criteria
- Notion page URLs resolve to page IDs and return a title plus flattened page text.
- Supported headings, paragraphs, lists, and tables are extracted across nested and paginated child blocks; unsupported blocks are skipped gracefully.
- Content is stored through Content acquisition: extend FetchResult + storage for full extracted text (precursor) #83's full-text storage and fetching is enabled for the Notion source.
- An unshared or inaccessible page produces an ingest warning while retaining the catalog record.
- Credentials are supplied securely through configuration, never logged, and access is limited to pages intentionally shared with the integration.
Notes / links
Disposition: Closed as not planned; do not implement or reopen as part of this cleanup. Parent epic: #82. These unchecked criteria describe canceled scope, not remaining delivery commitments.
Archived credential proposal: Prefer an internal integration token for explicitly shared pages; per-user OAuth was an alternative, not a chosen requirement. Any revived proposal must reconcile source access with #77.
Architecture note: The original proposal used an in-process catalog Fetcher. #82 later moved authenticated source adapters/credentials into services/connectors; revival would require re-scoping to that architecture rather than following the obsolete wiring instructions.
Out of scope: All implementation under the current project direction.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
andrei-akopian commentedon Sep 5, 2026
What do we have on notion?
[-]Notion content connector[/-][+]Fetch authenticated Notion page content[/+]