Start a Browserbase session for new Notion intake
When an intake page is added to a Notion database, start an isolated Browserbase session so the next browser task has a fresh workspace ready.
When something happens in Notion, Notis takes the next step in Browserbase Tool. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Fires when a new comment is created in the accessible workspace.
Do this · Action
Deprecated compatibility action for creating a browser context.
When an intake page is added to a Notion database, start an isolated Browserbase session so the next browser task has a fresh workspace ready.
When a Notion page is created, retrieve the relevant Browserbase session details so the team can review its current status and URLs.
When a Notion task's properties change to indicate browser work is done, ask Notis to request completion of its Browserbase session.
When a new Notion comment reports a browser problem, retrieve live debug URLs for the referenced Browserbase session for easier investigation.
When a Notion page's content changes to record a browser run, retrieve logs from the referenced Browserbase session for a reviewable run trail.
When a review page is added to a Notion database, download the artifacts from its completed Browserbase session for follow-up.
When a Notion queue item's properties are updated, list Browserbase sessions with the relevant status or metadata query to review active work.
When a new subpage is added beneath a project hub, create an isolated Browserbase session if the subpage describes work that needs browser access.
When a new Notion view is created for browser work, retrieve details for the Browserbase session described by the view context to make its status easier to inspect.
Notis builds workflows that link Notion to Browserbase Tool. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Deprecated compatibility action for creating a browser context.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Attaches an existing project secret to a Function for its next run.
Fires when a new comment is created in the accessible workspace.
Deprecated compatibility action for retrieving a browser context.
Fires when a new database container is created.
Updates a browser context to provide fresh upload and encryption details.
Fires when a new data source is created in the workspace.
Deprecated action for creating a browser session.
Fires when a data source’s columns are added, removed, or renamed.
Creates a reusable browser context.
Fires when the body content of an accessible page is updated.
Creates a reusable browser agent with an optional prompt and result schema.
Fires when a new page is created in the accessible workspace.
Creates an isolated browser session and returns its connection details.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Notion and Browserbase Tool, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Browserbase Tool.