Review available browser sessions as projects start
Before starting from scratch, check the existing Browserbase sessions when a new project enters Jira.
Trigger
New Project
Triggered when a new project is added in Jira
Action
List Browser Sessions
Tool to list all browser sessions. use when you need to retrieve sessions with optional filtering by status or metadata query.
Why this helps
Useful browser runs can be hard to spot when a new project starts and prior investigation context is scattered.
- See available sessions during project kickoff.
- Help reuse investigation context when it is relevant.
- Reduce duplicate browser setup and searching.
Setup
Build it in a few focused steps.
- 1Connect Jira and Browserbase tool once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to list Browserbase sessions when a new Jira project appears and summarize potentially relevant sessions using available context.
- 4Pick the Jira New Project trigger, then choose where run reports should go.
- 5Test with one real project creation and review the session listing.
Questions about this workflow
Can the workflow determine which sessions belong to a project?
It can use available session metadata and project context. Supply a useful matching clue if sessions do not contain project identifiers.
Does listing sessions change anything in Browserbase?
No. It retrieves a session listing for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Browserbase tool. A trigger fires from one place; an action lands in another.
Jira 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 Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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 Project
Triggered when a new project is added in Jira
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Jira 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.