Recheck sources when your notes change
Update a Notion research page and have Anchor browser retrieve the pages it references, so changes to your thinking come with source context.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get Webpage Content
Tool to retrieve rendered content of a webpage in html or markdown format. use when you need to fetch a page’s full content, optionally within an existing browser session.
Why this helps
Research notes evolve, but linked pages often remain unopened until a later review session.
- Pairs revised notes with fresh retrieval of referenced pages.
- Helps you spot source details relevant to the new direction.
- Cuts the friction of restarting research after a context switch.
Setup
Build it in a few focused steps.
- 1Connect Notion and Anchor browser to Notis once through the portal.
- 2Create an automation and write one plain-language instruction to retrieve referenced webpage content when a research page body changes.
- 3Choose the Notion Page Content Updated trigger, optionally scoped to a research data source, and choose a reporting channel.
- 4Test by editing one research page with a source link.
Questions about this workflow
Will it run for every page edit?
The trigger can be scoped to a data source, page, or parent page; without a scope, it fires for accessible page content edits across the workspace.
Are edits immediate?
Notion aggregates content edits within a short window, typically around 60 seconds.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Anchor browser. A trigger fires from one place; an action lands in another.
Notion triggers
Anchor browser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Profile
Tool to create a new browser profile from an active session. use after ending a session to persist cookies and cache.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Profile
Tool to delete a browser profile by id. use after confirming the profile exists.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
End All Sessions
Tool to end all active browser sessions. use after confirming a security concern when you need to immediately close every session for the authenticated user.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
End Browser Session
Tool to end a specific browser session by id. use after confirming the session id you want to terminate.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Profile
Tool to fetch details for a specific browser profile by id. use after you know the profile id and need its settings and session information.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get Webpage Content
Tool to retrieve rendered content of a webpage in html or markdown format. use when you need to fetch a page’s full content, optionally within an existing browser session.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
List Agent Resources
Tool to list agent resources (files) for a given session. use after establishing a browser session to retrieve agent-uploaded files.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
List All Sessions Status
Tool to list the status of all active browser sessions. use after authenticating when you need to retrieve an up-to-date overview of all sessions.
Connect any two apps with Notis in the middle.
Notion and Anchor browser, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Anchor browser.