Recheck links when issue details change
When issue details change, revisit the supporting pages and get a concise report on what loads now and what needs attention.
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
Fetch Webpage Content
Your eyes: get page content for decision-making. use before: actions (find targets, understand state) use to verify: page transitions, major state changes, when actions seem to fail format: html=find elements | markdown=clean content | success rate: 99%
Why this helps
A reference that worked earlier may have moved or changed, while the ticket continues to rely on its old context.
- Revisits ticket references after issue changes.
- Reports current page content for quick comparison with the issue.
- Calls out inaccessible or empty pages for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Jira and Browser tool once in the Notis portal.
- 2Create an automation and name it for rechecking issue links.
- 3Tell Notis to fetch webpage URLs in an updated issue and report page availability, a concise content summary, and any obvious change relevant to the issue details.
- 4Pick the Jira Updated Issue trigger for the project.
- 5Select a report channel and test using one real updated issue with a reference URL.
Questions about this workflow
Can Notis know what the page looked like before?
Only if that earlier content is supplied in the issue or prompt. This workflow can report the current fetched content, but the trigger does not provide a page history.
Will it update the Jira ticket?
No. It fetches webpage content and provides a report; the allowed Browser tool actions do not write to Jira.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Browser tool. A trigger fires from one place; an action lands in another.
Jira triggers
Browser tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Copy Selected Text
Copy currently selected text on the page to clipboard - ideal for extracting highlighted content, copying form data, or harvesting visible text selections.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Drag and Drop
Execute precise drag and drop operations - essential for file uploads, list reordering, element moving, and complex ui interactions that require drag-based manipulation.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Fetch Webpage Content
Your eyes: get page content for decision-making. use before: actions (find targets, understand state) use to verify: page transitions, major state changes, when actions seem to fail format: html=find elements | markdown=clean content | success rate: 99%
New Project
Triggered when a new project is added in Jira
Get Clipboard Content
Read current content from the system clipboard - essential for data transfer workflows, extracting copied text, and reading user-copied data for processing.
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.
Keyboard Shortcut
Execute keyboard shortcuts and key combinations - essential for copy/paste, navigation, and application commands that agents need for efficient browser automation.
Mouse Click
Precision clicker: manual clicking with coordinates. pattern: fetchwebpage(html) → find element → estimate coordinates → click → verify hints: center buttons ~(640,350) | nav/header ~y=150 | content ~y=300-500 tip: try ±50px if first click misses | success rate: 85%
Mouse Double Click
Execute a precise double click at specified screen coordinates - ideal for opening files, selecting text, or activating ui elements that require double click gestures.
Mouse Down (Press and Hold)
Press and hold mouse button at coordinates - use for starting custom drag operations, text selections, or long-press interactions. must be followed by mouseup action to complete.
Connect any two apps with Notis in the middle.
Jira and Browser 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 Browser tool.