Keep Jira updates grounded in current page content
When an issue changes, Notis can ask Browserless to fetch the relevant page details and report them beside the updated ticket context.
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
Scrape webpage content using CSS selectors
A tool to extract structured content from a webpage by specifying css selectors. the tool navigates to the specified url, waits for the page to load (including parsing and executing javascript), and returns the selected elements in a structured json format.
Why this helps
A changed ticket can leave the team comparing old notes with a page that has changed since the issue was filed.
- Review selected page content when an issue changes.
- Avoid reopening a browser and hunting for the same page details.
- Keep the current page snapshot tied to the Jira update that prompted it.
Setup
Build it in a few focused steps.
- 1Connect Jira and Browserless once in the Notis portal.
- 2Create an automation named Refresh reference page details.
- 3Tell Notis to use the updated issue context to scrape the relevant URL with suitable CSS selectors and summarize the returned content.
- 4Pick the Jira Updated Issue trigger for the project you configure.
- 5Choose a report channel, then test with one updated issue that includes a page URL and known selectors.
Questions about this workflow
What changes start this automation?
The Updated Issue event fires when an existing issue in the configured Jira project changes, such as status, assignee, or another issue field. Comment activity does not trigger it.
Does Browserless know which selectors to use?
The scrape action requires CSS selectors. Include the selectors in your instruction or provide enough context for Notis to determine appropriate ones.
What if the issue has no URL?
The trigger supplies Jira issue context, but it does not create a page URL. Provide a URL in the issue or in your instruction for the scrape to run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Browserless. A trigger fires from one place; an action lands in another.
Jira triggers
Browserless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Download file using Puppeteer script
This tool allows downloading files that chrome has downloaded during the execution of puppeteer code. it sets up a blank page, creates a fresh download directory, injects the provided code, and executes it. once the script finishes, any downloaded files from chromium are returned with the appropriate content-type header.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Custom Function
A tool that allows executing custom puppeteer scripts via http requests. this endpoint enables users to run browser automation tasks without managing their own infrastructure.
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 HTML Content
This tool fetches the complete html content of a webpage using browserless's content api. it's designed to retrieve the full html contents of any website, including dynamically generated content.
New Project
Triggered when a new project is added in Jira
Generate PDF from webpage
This tool generates a pdf from a specified webpage using browserless's pdf generation api. it allows specifying the url of the webpage along with parameters such as format, filename, and waituntil options to control the pdf generation process.
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.
Scrape webpage content using CSS selectors
A tool to extract structured content from a webpage by specifying css selectors. the tool navigates to the specified url, waits for the page to load (including parsing and executing javascript), and returns the selected elements in a structured json format.
Take Screenshot
A tool that captures a screenshot of a webpage using browserless's screenshot api. the tool takes a url and returns either a png or jpeg image. it includes options for full page capture, image type, quality, and clipping coordinates.
Unblock Protected Content
This tool provides access to content from websites that implement bot protection mechanisms. it is designed to bypass various types of protection (such as captcha and bot detections) and return the html content of the protected webpage, with optional customization through parameters like waitfor, timeout, and stealth mode.
Connect any two apps with Notis in the middle.
Jira and Browserless, 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 Browserless.