Start browser follow-up when an issue changes
When an issue change calls for a browser check, create a remote session from the same workflow.
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
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
Why this helps
Browser follow-up can get lost when a ticket changes and the next investigation step is handled elsewhere.
- Start a remote session in response to an issue update.
- Keep browser follow-up connected to the changed ticket.
- Make the need for investigation easier to track.
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 which issue changes should start a browser session.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue change that calls for browser follow-up.
Questions about this workflow
Does every issue update create a session?
The listed event fires for issue changes in the configured project. State in the instruction when an update should start a session.
Does this perform the browser follow-up?
This action creates a remote browser session. The available action description does not specify further navigation or browser steps.
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.