Skip to content
Notis

Keep documentation link issues current in Jira

Catch dead links in product documentation during a scheduled browser pass, then keep the relevant Jira tracking issue up to date.

Trigger

Recurring schedule

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

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

Broken links are easy to miss across a growing help center, and repeated manual checks interrupt other work.

  • Check the documentation URLs you specify on a recurring schedule.
  • Record affected page URLs and failing destination links in Jira.
  • Update a tracking issue with newly observed findings.

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, list the documentation pages and Jira issue to maintain, and ask Notis to add newly observed broken links with their source URLs.
  • 4Pick a recurring schedule and choose where run reports go.
  • 5Test with one real documentation page and review the updated Jira issue.

Questions about this workflow

Can this check an entire site?

Specify the pages or sitemap URLs you want checked. Do not assume the automation can discover every page unless you ask it to navigate and inspect the relevant site structure.

What should the Jira issue contain?

Ask Notis to include the source page, destination URL, and observed failure detail so someone can verify and repair the link.

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.