Catch changed language requests without another manual lookup
When a learner's language preference changes, refresh the available language list and flag whether the new request is covered.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Fetch Available Languages
Tool to retrieve the list of available languages. use when you need to verify supported languages before starting a placement test.
Why this helps
An edited language preference can leave an outdated assumption in place unless someone remembers to check again.
- Recheck the current language list after a learner detail changes.
- Reduce follow-up work caused by stale language assumptions.
Setup
Build it in a few focused steps.
- 1Connect Notion and Linguapop to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to review language support after learner property updates.
- 3Write one plain-language instruction asking Notis to retrieve the available languages and assess the updated request.
- 4Select the Notion Page Properties Updated trigger for the learner database and choose a reporting channel.
- 5Test by updating one real learner's requested language.
Questions about this workflow
Does every property edit cause a check?
The selected trigger fires on property updates in the chosen data source; the instruction can focus Notis on language-related changes.
Can the action change the learner record?
No. The available action only retrieves Linguapop's available languages.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Linguapop. A trigger fires from one place; an action lands in another.
Notion triggers
Linguapop actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Fetch Available Languages
Tool to retrieve the list of available languages. use when you need to verify supported languages before starting a placement test.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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 Linguapop, 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 Linguapop.