Skip to content
Notis

Refresh Browserbase context details as issue work changes

Keep upload setup current by refreshing details for the existing browser context tied to an active investigation.

Trigger

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.

Action

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.

Why this helps

Reusing an existing context can stall when fresh upload details are needed and nobody remembers to retrieve them.

  • Retrieve fresh upload URL and encryption details for an existing context.
  • Support continued context setup during active issue work.
  • Reduce interruption when context upload details need refreshing.

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 update the existing Browserbase context related to an updated issue to obtain fresh upload URL and encryption details, using its context id.
  • 4Pick the Jira Updated Issue trigger, then choose where run reports should go.
  • 5Test with one real issue and a valid context id, then review the run report.

Questions about this workflow

Does this action create a context?

No. It updates a specific existing context and retrieves fresh upload URL and encryption details.

What identifier does it need?

It needs a valid Browserbase context id. Make that id available to Notis from the issue context or another supplied source.

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.

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

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

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

New Project

Triggered when a new project is added in Jira

TriggerInstant

Create Browser Session

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

ActionInstant

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.

TriggerInstant

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

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

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

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

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.