Check Model Country Restrictions from a Notion Launch Plan
Create a launch plan in Notion and have Notis retrieve Apipie ai's model country restrictions for review.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
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.
Why this helps
Country eligibility checks are easy to forget when a launch plan is moving quickly across tools.
- Bring country restrictions into the launch planning process early.
- Reduce the need to remember a separate eligibility lookup.
- Give reviewers a timely reference before choosing a model.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apipie ai to Notis once through the portal.
- 2Create an automation in the portal with a prompt asking Notis to retrieve Apipie ai model country restrictions for new launch plans.
- 3Choose the Notion Page Created trigger and a channel for run reports.
- 4Test with one actual launch plan and review the restriction information.
Questions about this workflow
Does the lookup approve a deployment?
No. It retrieves country restrictions for review; your team decides whether a model fits the intended deployment.
Can I scope this to a launch-plan database?
The Notion trigger supports a data source scope where available. Describe the intended launch plans in the prompt as well.
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.