Get a fresh page capture when an issue changes
A status or field update can signal that a page is ready for another look. Capture the URL supplied in the updated issue for a timely visual review.
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
Capture Screenshot
Tool to capture a webpage screenshot. Use when you need a visual snapshot of a URL or HTML with optional viewport and clipping.
Why this helps
A changed issue can prompt follow-up, but the team may still need to reopen its page and capture the latest view.
- Use any qualifying issue update as a cue for a fresh page capture.
- Keep the screenshot request close to the changed issue context.
- Skip updates without a usable URL.
Setup
Build it in a few focused steps.
- 1Connect Jira and Cloudflare browser rendering once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Ask Notis in one instruction to capture a screenshot of the URL in an updated issue when present.
- 4Pick Jira Updated Issue as the trigger and select a report destination.
- 5Test with one real issue update that includes a webpage URL.
Questions about this workflow
Which Jira changes can start this workflow?
The Updated Issue event fires when an existing issue in the configured project changes, including status, assignee, or another issue field. It does not fire for comment activity.
Does the workflow know whether the page itself changed?
The event indicates that the Jira issue changed. It does not establish whether the webpage changed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Cloudflare browser rendering. A trigger fires from one place; an action lands in another.
Jira triggers
Cloudflare browser rendering actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Capture Screenshot
Tool to capture a webpage screenshot. Use when you need a visual snapshot of a URL or HTML with optional viewport and clipping.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Accounts
Tool to list all Cloudflare accounts accessible. Use to retrieve a valid account_id for further browser rendering actions.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Scrape HTML Elements
Tool to scrape HTML elements for text, HTML, attributes, and box metrics. Use when you need detailed data of matched selectors after rendering a page.
New Project
Triggered when a new project is added in Jira
Take Webpage Snapshot
Tool to capture rendered HTML and screenshot of a webpage. Use when you need both DOM content and an image in one request with custom loading and capture settings.
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.
Connect any two apps with Notis in the middle.
Jira and Cloudflare browser rendering, 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 Cloudflare browser rendering.