Skip to content
Notis

Keep browser evidence with the Jira issue

When a ticket needs a quick web check, start the browser review with a request and put relevant evidence alongside the existing Jira work.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Evidence gathered in a separate browser session is easy to lose before the Jira ticket is updated.

  • Start a page inspection when an HTTP request arrives.
  • Update the Jira issue named in the request with observed evidence.
  • Keep source URLs and relevant page details next to the work.

Setup

Build it in a few focused steps.

  • 1Connect Browserbase MCP and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, ask Notis to inspect the requested page and update the specified Jira issue with relevant observations and source links.
  • 4Pick a webhook trigger and choose where run reports go.
  • 5Test with one real page URL and an existing Jira issue.

Questions about this workflow

What information should the request provide?

Provide the page URL, the Jira issue key, and what evidence to look for. The automation can only inspect accessible page content.

Will this create another issue?

No. It updates the existing Jira issue specified in the request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Browserbase MCP to Jira. A trigger fires from one place; an action lands in another.

Browserbase MCP triggers

Jira actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Browserbase MCP and Jira, 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 Jira.