Skip to content
Notis

Start a site crawl when a content brief is refreshed

Refresh your brief in Notion and let Hyperbrowser gather the pages needed for your next content pass.

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

Start Crawl Job

Tool to start a new crawl job for a specified URL. Use when you need to initiate a web crawl before checking job status.

Why this helps

A refreshed content plan can still depend on stale assumptions if nobody remembers to revisit the site.

  • Tie a site review to the moment the brief changes.
  • Gather a page batch for content planning in one step.
  • Reduce the chance that a revised brief uses outdated site context.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Hyperbrowser to Notis once in the portal.
  • 2Create the automation in the portal or ask Notis conversationally.
  • 3Write one instruction explaining which brief edits should start a crawl and which site URL to crawl.
  • 4Select the Notion Page Content Updated trigger for the brief page and choose a run-report channel.
  • 5Test by making a meaningful content edit to a brief with its target site URL.

Questions about this workflow

Does the crawl include every site page?

Crawl coverage depends on the target site and Hyperbrowser job behavior. Review the job results for the pages it returns.

Can I limit this to one brief?

The Page Content Updated trigger supports a specific page, data source, or parent page scope. Choose the relevant scope when setting up the trigger.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Hyperbrowser. A trigger fires from one place; an action lands in another.

Notion triggers

Hyperbrowser actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Hyperbrowser Profile

Tool to create a new profile. Use when you need to initialize a Hyperbrowser profile before analysis.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Scrape Job

Tool to initiate a new scrape job. Use when you need to extract structured content from a target URL with custom session and scrape settings.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Create Session

Tool to create a new browser session with custom stealth, proxy, and privacy settings. Use when initializing an automated browsing session with specific configuration.

ActionInstant

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.

TriggerInstant

Delete Profile

Tool to delete a profile. Use when you need to remove a profile by its unique identifier after confirming its existence.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get browser-use task status

Tool to retrieve the current status of a browser-use task. Use when checking if a browser automation task has completed or is still pending.

ActionInstant

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.

TriggerInstant

Get Claude Computer Use Task Status

Tool to retrieve the status of a Claude Computer Use task. Use after creating a task to poll its status.

ActionInstant

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.

TriggerInstant

Get Crawl Job Result

Tool to retrieve the result of a completed crawl job. Use after confirming crawl job completion to fetch current page batch and status. Supports pagination via page and batchSize.

ActionInstant

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.

TriggerInstant

Get Crawl Job Status

Tool to retrieve the status and results of a specific crawl job. Use after submitting a crawl job to check its progress or fetch results.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Hyperbrowser, 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 Hyperbrowser.