Review Apipie ai Query History from a Notion Cost Review
Update the cost review in Notion and have Notis fetch Apipie ai usage history to support the next review.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
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 analysis gets postponed when historical API activity lives apart from the team's cost review notes.
- Bring historical usage data into a review that is already being updated.
- Make latency, token, and cost signals easier to inspect together.
- Reduce manual follow-up to gather the inputs for a usage audit.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apipie ai to Notis once through the portal.
- 2Create an automation with a plain-language prompt to retrieve Apipie ai query history when the cost review content is updated.
- 3Select the Notion Page Content Updated trigger, scoped to the review page if appropriate, and choose a reporting channel.
- 4Test by updating one cost review page and checking the retrieved history.
Questions about this workflow
What does query history include?
The listed Apipie ai action retrieves historic API usage logs, including latency, token counts, costs, and source IP.
Will the workflow calculate savings?
The action retrieves logs. You may ask Notis to summarize patterns from the returned data, but the source action is the history lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Apipie ai. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.