PageCrawl can write every detected change into a Notion database as a new row. Nobody has to copy anything across, and the record sits in the workspace where the decision gets made rather than in an inbox.
This is the direct integration, where PageCrawl writes the rows itself on its own schedule. If you would rather have a Notion agent decide what to write and when, connect the MCP server to a Notion custom agent instead. The two can be used together.
How It Works
When a check detects a change, PageCrawl creates one page (a row) in your chosen Notion database, filling the properties you selected. Rows are only ever created, never overwritten, so the database becomes a running history.
A monitor's first check is a baseline rather than a change, so it does not produce a row.
Setting It Up
- Go to Settings > Integrations and find the Notion card
- Click Connect. Notion asks you to sign in and then shows a page picker
- Choose the pages or databases PageCrawl should have access to. This is the step that matters: PageCrawl can only see what you grant here
- Back in PageCrawl, click Manage and choose:
- What to write: a change log, or a review board that adds a Status property
- Where it goes: a database you already have, or let PageCrawl create one
- Properties to write: the fields that become Notion columns
If you point at an existing database, PageCrawl adds any properties you selected that it does not already have. Existing properties and rows are left alone.
Available Properties
Each property you tick becomes a Notion column of a matching type:
| Field | Notion type | What it holds |
|---|---|---|
| Title | Title | The monitor's name |
| URL, View, Screenshot | URL / Files | Links to the page, the change in PageCrawl, and the capture |
| Changed at | Date | When the change was detected |
| Importance, Difference % | Number | The AI priority score, and how much of the content changed |
| Domain, Folder, Type | Select | Facets you can group or filter a Notion view by |
| Labels | Multi-select | One option per label on the monitor |
| Summaries, values, diffs | Text | The short summary, AI summary, and the current and previous values |
Long values are split across multiple text blocks rather than cut off, so a full AI summary survives intact.
Choosing a Mode
Change log is the plain record: a row per change, newest at the top. Use it when the value is the history.
Review board adds a Review property with To review, In progress, Actioned and Ignored. PageCrawl sets a new row to "To review" and never touches that property again, so moving a card in Notion is never undone by a later sync. Use it when a person has to decide something about each change.
When Sync Stops
PageCrawl pauses the sync and notifies your workspace when Notion says the connection is gone. The two causes:
- Access was removed in Notion, or the connection was revoked
- The database was deleted, moved to trash, or unshared from PageCrawl
The card in Settings > Integrations shows which happened. Reconnect to resume. Your existing rows are untouched either way.
Common Questions
Does this replace the Google Sheets sync?
No, they are independent and can both run. Sheets suits analysis on the numbers; Notion suits a team that already works in Notion and wants to comment, assign and file the change alongside everything else.
Can I sync only some monitors?
Per-monitor selection is available through the API today. In the dashboard, the sync currently covers every monitor in the workspace, so use a separate workspace if you want a narrower set.
How soon does a row appear?
A row is written after a check detects a change, so the monitor's check frequency decides the delay. Sync failures retry on their own with a growing gap, and Notion's own rate limits are respected rather than worked around.
Is my Notion token safe?
The access token is encrypted at rest, is never returned by the API, and is never written to logs. PageCrawl only ever reaches the pages and databases you granted in Notion's picker.