WorkSights integrates with Notion to bring document activity and collaboration signals directly into the activity timeline. When mapped users create or update pages, change page properties, add comments, or work within databases in Notion, WorkSights receives metadata and displays it as structured timeline entries.

Only activity that occurs after the integration is connected will appear. WorkSights does not import historical Notion data.

For connection steps, see Notion Setup.

What WorkSights Receives

WorkSights receives metadata for the following Notion activity:

Pages

Page creation, content edits, and property changes appear as document activity. Page body content is never received - only metadata describing that a change occurred.

Database rows

Every Notion database row is technically a page, so row creation and edits appear as page activity, with the database name included in the breadcrumb title.

Comments

When a user adds a comment to a page, WorkSights records the event and includes a preview of the comment text in the activity detail.

Files

File uploads and changes appear as activity entries, though file content and metadata beyond the event itself are not retrieved.

Each entry includes the user who performed the action, the page or document affected, the workspace hierarchy leading to it, and the timestamp.

How Notion Activity Appears

Page activity shows a hierarchical breadcrumb title built from the page’s parent chain, for example Workspace > Project Docs > Meeting Notes. Multiple edits to the same page within a short window are consolidated into a single activity rather than creating a separate entry for each change.

Database structural changes like creating a new database or changing its schema produce minimal activity, since these are structural actions rather than work performed by a team member. Row-level edits within a database are different: because each row is a page, adding or editing rows generates regular page activity with the database name shown in the breadcrumb. Adding five rows to a board, for example, appears as five separate page-creation activities.

Comments appear with the page’s breadcrumb title, and the activity detail includes a preview of the comment text.

Page activity is categorized as Task. Comments, file events, and database structural changes are categorized as General.

Users and Guests

WorkSights imports Notion workspace members and matches them to WorkSights users by email address. Mapping is refreshed daily. Only person-type users are ingested. Notion bot users are excluded.

If an event arrives for a user who isn’t yet mapped, WorkSights holds the event and retries as mapping is refreshed, rather than dropping it immediately.

Notion guests (people with access to specific pages but not full workspace members) are handled separately. If a guest’s identity resolves to a known client contact, their activity appears as client-authored activity on ClientSights rather than as scored WorkSights activity. If a guest doesn’t resolve to either a mapped WorkSights user or a known client contact, their events are not captured.

Integration Page Overview

The Notion integration page contains three tabs:

• Overview - Connection status and integration owner
• Users - Notion users mapped to WorkSights users by email
• Connections - Connected Notion workspace and refresh controls

Data Notes

WorkSights ingests only the metadata required to represent Notion activity: page titles, timestamps, workspace hierarchy, user identity, and comment text previews. Page body content, file contents, and database content beyond row titles are never received or stored.

The integration follows Notion's permission model and is limited to the specific pages and databases shared with WorkSights during setup. See Notion Setup for details on how this access works and how to expand it.

Troubleshooting

Notion activity is not appearing as expected

Confirm the affected user is mapped by email in the Users tab. Bot users are intentionally excluded and will never generate activity.

The most common cause of missing activity is that the page or database in question hasn't been shared with the WorkSights integration in Notion. Notion's access model is page-specific, not workspace-wide. See Setup for how to check and update shared pages.

New pages aren't showing up even though the parent teamspace is shared

This is expected unless the new page was explicitly shared. New root-level pages (even ones created inside an already-shared teamspace) are not automatically included. Go to Notion's own Settings → Connections → WorkSights and add the missing pages or databases. There's no need to disconnect and reconnect WorkSights to apply this.

A database itself doesn't appear as activity when it's created

This is expected. Database creation and schema changes are structural actions and produce minimal activity by design. Row-level edits within the database will appear as regular page activity.

Activity shows Untitled or a generic name

The page may not have a title yet, or the lookup that builds the title failed. Adding a title in Notion will be picked up on the next edit.

Activity appears delayed

Activity is processed in batches roughly every 20 minutes. If a user was only recently mapped, their backlog of activity will appear on the next processing cycle once mapping completes.

Related Guides

Notion Setup