Bring Apipie query history into issue follow-up
When an issue changes, pull recent Apipie AI usage history into a run report for easier 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
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
Usage checks can slip when issue updates and API monitoring happen in separate places.
- Retrieve usage data alongside a relevant Jira issue update.
- Review latency, token counts, costs, and source IPs from available history.
- Make usage review easier to pick up during issue follow-up.
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: when an issue is updated, retrieve Apipie AI query history and summarize the available usage details.
- 4Choose the Jira Updated Issue trigger and select where run reports should go.
- 5Test with one real issue update and review the report.
Questions about this workflow
Does this trigger on Jira comments?
No. The Updated Issue event does not fire for comment activity such as adding, editing, or deleting a comment.
What usage details can the history include?
The action retrieves historic API usage logs including latency, token counts, costs, and source IPs.
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.