Connect Box to Browserbase tool

When something happens in Box, 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

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Box to Browserbase tool

View example

Review Browserbase session logs from a Box comment

When a Box comment identifies a Browserbase session, retrieve its logs and summarize notable network events and data exchanges.

View example

Find Browserbase debug links from a Box file comment

When a new comment on a Box file includes a running Browserbase session ID, retrieve its live debug URLs and report them with the file context.

View example

Retrieve completed Browserbase artifacts from a Box folder update

When a new item is added to a Box folder used to record completed Browserbase runs, retrieve the referenced session's artifacts for review.

View example

Check Browserbase session status when a Box task changes

When a Box task changes, retrieve the Browserbase session details for the session ID in its task context and include the status in the report.

Supported Triggers and Actions

Notis builds workflows that link Box to Browserbase tool. A trigger fires from one place; an action lands in another.

Box triggers

Browserbase tool actions

Recurring trigger

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

TriggerScheduled

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.

ActionInstant

Webhook trigger

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

TriggerInstant

Retrieve a browser context

Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.

ActionInstant

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

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.

ActionInstant

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

Create Browser Session

Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

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).

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

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.

ActionInstant

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

Download Session Artifacts

Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.

ActionInstant

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

Retrieve Session Logs

Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

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.