Close browser sessions when downstream work finishes
External completion signals can close browser work without another manual check.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Browser Session
Tool to update the status of a specific browser session. use when you need to request session completion before timeout to avoid additional charges.
Why this helps
Sessions remain active after downstream systems have finished using them.
- Reduce lingering sessions
- Lower avoidable runtime costs
- Keep lifecycle ownership clear
Setup
Build it in a few focused steps.
- 1Connect Outlook and Browserbase in Notis, then open Automations > New Automation.
- 2Describe how the webhook identifies the Browserbase session that should request completion.
- 3Pick an HTTP webhook as the trigger.
- 4Choose a report destination and test with one completion signal.
Questions about this workflow
What if the session is already closed?
Have Notis report its current status and avoid repeating the request.
Can this be used for batch cleanup?
Yes. Include the session identifiers or criteria in the webhook payload.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Outlook to Browserbase tool. A trigger fires from one place; an action lands in another.
Outlook 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.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
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.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
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).
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
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.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
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.
Outlook 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.