Refresh web context when Jira issues change
When a ticket changes, revisit its supplied source page and make updated context easier to 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
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Why this helps
A changed ticket can leave its web research stale, making people repeat searches or rely on old notes.
- Recheck a supplied page after issue fields change.
- Make refreshed details available in the run report.
- Help reviewers notice when outside context may have changed.
Setup
Build it in a few focused steps.
- 1Connect Jira and AgentQL once in the Notis portal.
- 2Create an automation in the portal or tell Notis to create one.
- 3Describe the outcome in one instruction and identify the issue reference URL.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue that has a reference URL.
Questions about this workflow
Does this run for comment activity?
The Jira Updated Issue event does not fire on comment activity. It fires when an issue field changes in the configured project.
Can it compare page history?
The listed AgentQL action queries a page. Historical comparison requires a baseline supplied by you or available in the provided context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Agentql. A trigger fires from one place; an action lands in another.
Jira triggers
Agentql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Usage Details
Tool to retrieve subscription usage details for the current api key, including usage limits and billing period. use after confirming api connection is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
New Project
Triggered when a new project is added in Jira
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 Agentql, 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 Agentql.