Review AgentQL usage on a schedule
Keep subscription usage and billing period visible in a recurring report for the people responsible for Jira project work.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Usage limits and billing periods are easy to overlook when they live outside the team's normal project review routine.
- Retrieve usage limits and billing period on a recurring schedule.
- Give Jira project owners a predictable point to review AgentQL usage.
- Reduce the need to remember a separate manual check.
Setup
Build it in a few focused steps.
- 1Connect AgentQL once in the Notis portal and confirm the API connection is valid.
- 2Create an automation in the portal or tell Notis to create one.
- 3Describe the outcome in one instruction: retrieve usage details and summarize them for Jira project owners.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real run and check the returned usage details.
Questions about this workflow
Why does this workflow use a schedule?
AgentQL's usage action retrieves usage details for the current API key, so a recurring check can make limits and billing period easier to review.
Does this read Jira project data?
No Jira event is required here. The workflow uses a Notis schedule and the AgentQL usage action.
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.