Keep browser run logs close to the run notes
When run notes are updated, retrieve logs for the session they describe and make troubleshooting context easier to find.
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
Retrieve Session Logs
Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
Why this helps
Troubleshooting takes longer when browser logs are separate from the notes describing a run.
- Retrieve session logs when run notes are updated.
- Keep the event trail closer to the team's explanation of a browser run.
- Reduce the steps needed to gather troubleshooting context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Browserbase tool to Notis once through the portal.
- 2Write one plain-language automation prompt explaining which content update represents a run note and where its Browserbase session can be identified.
- 3Select the Notion Page Content Updated trigger scoped to the relevant page or database.
- 4Choose a run-report channel and test with a note linked to a completed session.
Questions about this workflow
Does this retrieve logs for any page edit?
Choose an appropriately scoped content trigger and explain in the prompt which updated notes represent browser runs.
Can it retrieve logs before the session has activity?
Session logs are most useful after actions have occurred. Test with a session that has a run history.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Browserbase tool. A trigger fires from one place; an action lands in another.
Notion triggers
Browserbase tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new browser context
Tool to create a new browser context. use when you need to obtain upload credentials for a custom user-data-directory in a project.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve a browser context
Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Update Browser Context
Tool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.
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.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Retrieve a browser session
Tool to retrieve details of a specific browser session. use when you have a session id and need its metadata (status, urls, timestamps).
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.
Retrieve Session Debug URLs
Tool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.
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.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
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.
Retrieve Session Logs
Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
Connect any two apps with Notis in the middle.
Notion and Browserbase tool, 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 Browserbase tool.