Skip to main content
The Notion connector mounts content shared with the Locality integration. The connector contract supports All content shared with Locality as well as an explicit restricted roots scope. The hosted all-shared rollout is staged; until it is enabled for an organization, Locality Cloud continues to ask for explicit roots and applies the 16-root limit. The connector emits bounded change pages and resumable checkpoints. When the hosted durable-hydration rollout is enabled, the UI reports Discovering content, Hydrating X / Y, Publishing, and Ready. If automatic retries are exhausted, Needs attention includes a safe reason, manual Retry, and a diagnostic ID suitable for support.

​
Connect

Development token fallback:

​
Mount

Workspace mount:
Specific root page:

​
Projection

  • pages are directories;
  • page bodies live in page.md;
  • child pages live under parent page directories;
  • databases are directories;
  • database schemas live in _schema.yaml;
  • database rows are page directories.

​
Supported writes

Locality currently supports conservative Notion writes:
  • update, append, archive, and move selected simple blocks;
  • update supported page properties;
  • create new rows in single-data-source databases;
  • update local file-like media for supported media blocks;
  • reconcile changed pages after push.
Unsupported or lossy Notion structures are preserved as ::loc{...} directives and block unsafe pushes when needed.

​
Databases

The word database in Locality UI means a Notion database-like object. It is projected as a directory, not as a hidden Locality database. Before pushing row property edits, Locality validates supported properties against _schema.yaml.

​
Common Notion errors

​
Agent rule

When creating or moving content, the containing directory determines the Notion parent. Do not choose a parent by matching titles from search results.