Keep AI usage review on the calendar
A recurring report makes it easier to revisit Apipie AI usage while your team moves Jira work forward.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get query history
Tool to retrieve historic api usage logs including latency, token counts, costs, and source ip. use after authenticating to analyze past queries for cost management, performance monitoring, or auditing.
Why this helps
API usage is easy to overlook when nobody has a clear moment set aside to review it.
- Set a regular moment to review available API usage history.
- Bring costs and performance details to team attention.
- Reduce reliance on memory for recurring operational checks.
Setup
Build it in a few focused steps.
- 1Connect Jira and Apipie AI once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe: retrieve Apipie AI query history and summarize costs, latency, token counts, and source IPs for review.
- 4Choose a recurring schedule trigger and select where run reports should go.
- 5Test with one run and review the report.
Questions about this workflow
Does the schedule report only Jira-related API calls?
The action retrieves Apipie AI query history. It does not establish which queries relate to Jira unless that information is available in the returned data or you supply criteria.
Can the report compare usage with a prior period?
Only if the needed baseline or historical comparison is supplied or present in the returned data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Apipie ai. A trigger fires from one place; an action lands in another.
Jira triggers
Apipie ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Vectors
Tool to delete an entire vector collection or specific vectors. use when you need to remove vector data after identifying your target collection or vectors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Fetch model restrictions
Tool to retrieve a list of country restrictions for models. use when you need to verify allowed deployment countries before final model selection.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get query history
Tool to retrieve historic api usage logs including latency, token counts, costs, and source ip. use after authenticating to analyze past queries for cost management, performance monitoring, or auditing.
New Project
Triggered when a new project is added in Jira
List AI Models
Tool to fetch a list of available ai models. use when you need up-to-date model listings and want to filter by. model type, subtype, provider, or retrieve specialized lists like voices or restrictions.
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 Apipie ai, 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 Apipie ai.