Look up Browserbase context details on demand
Get context metadata when a workflow or teammate needs to inspect a specific Browserbase context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve a browser context
Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.
Why this helps
Context IDs and metadata are easy to lose when browser setup is handled across multiple tools.
- Look up context information from a simple request.
- Reduce manual navigation when investigating browser setup.
- Keep context details available in the run report.
Setup
Build it in a few focused steps.
- 1Connect Browserbase tool once in the Notis portal.
- 2Create an automation in Notis and give it a clear name.
- 3Describe the outcome in one instruction: retrieve metadata for the Browserbase context ID provided in the webhook request and report the result.
- 4Pick an HTTP request webhook as the trigger and choose where run reports should go.
- 5Test with one real context ID.
Questions about this workflow
What does the request need to contain?
It needs the ID of the Browserbase context to retrieve.
Can this create or update a context?
No. This workflow retrieves details for an existing context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Browserbase tool. A trigger fires from one place; an action lands in another.
Asana 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.
Attachment Added to Task
Triggers when an attachment is added to a task.
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.
New Comment on Task
Triggers when a comment is added to a task in a project.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
New Task Created
Triggers when a new task is created in a project.
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).
Task Moved to Section
Triggers when a task is moved to a section in a project.
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.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
Task Updated
Triggers when a task is updated in a project.
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.
Asana 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.