Start a Browserbase session from a 2chat request
Send a browsing request through your 2chat workflow and have Notis open an isolated Browserbase session for the next step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
Why this helps
Browser tasks can stall while you switch from a WhatsApp conversation to a separate browser setup.
- Start an isolated browser session from an incoming request.
- Keep the request and resulting session in one automation run.
- Reduce manual handoff between chat and browser setup.
Setup
Build it in a few focused steps.
- 1Connect 2chat and Browserbase once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to create a Browserbase session for each incoming webhook request and summarize the returned session details.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one real example request sent through your 2chat workflow.
Questions about this workflow
Does this trigger on every 2chat message automatically?
No. This workflow starts when a webhook request reaches Notis. Your 2chat workflow or another caller must send that request.
Does creating the session browse a website?
No. The selected action creates a Browserbase session. Page interactions require a separate supported step outside this action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Browserbase tool. A trigger fires from one place; an action lands in another.
2chat 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.
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.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
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).
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.
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.
2chat 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.