Keep browser profiles easy to review
Let Notis bring your Hyperbrowser profiles into a monthly review so you can decide which setups are still relevant.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Profiles
Tool to list profiles. Use when you need to fetch paginated profiles and optionally filter by name.
Why this helps
Profiles created for short projects can become hard to distinguish from the browser setups you still rely on.
- Make browser profiles visible on a regular cadence.
- Revisit which setups still serve current work.
- Reduce uncertainty about where a research task should start.
Setup
Build it in a few focused steps.
- 1Connect Hyperbrowser to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally to run monthly.
- 3Describe that the workflow should list profiles and summarize their names for a review.
- 4Choose a monthly Notis schedule and select a channel for run reports.
- 5Review the first run and decide manually whether any profile needs action.
Questions about this workflow
Does this delete unused profiles?
No. It lists profiles for review. Deleting a profile is a separate action that should be chosen deliberately.
Can the list be narrowed?
The list profiles action can optionally filter by name. State a useful naming pattern in the instruction if applicable.
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.