Collect sources as you set up a research view
Create a focused research view in Notion and start collecting its named web sources without another manual handoff.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
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.
Why this helps
A fresh research view can sit ready for work while source gathering remains a separate task to remember.
- Connect research organization to an immediate source-gathering step.
- Avoid postponing collection after setting up a view.
- Keep the intended site close to the workflow that will use it.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hyperbrowser to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set it up conversationally.
- 3Describe which new research views should trigger a scrape and how Notis should find the target URL in the workspace context.
- 4Select the Notion View Created trigger and choose a channel for run reports.
- 5Test by creating a research view with its source URL available in the related context.
Questions about this workflow
Does a view contain the source URL?
Not necessarily. The automation instruction and related Notion context need to identify the target URL for the scrape.
Can I use this for any view?
The trigger is workspace-wide. Describe the research view types or context that should qualify.
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.
Create Hyperbrowser Profile
Tool to create a new profile. Use when you need to initialize a Hyperbrowser profile before analysis.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
Delete Profile
Tool to delete a profile. Use when you need to remove a profile by its unique identifier after confirming its existence.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 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.
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.
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.
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.
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.
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.