Get language codes from new expansion ideas
Capture a target language in Notion and receive its supported Google code as a useful research starting point.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
Why this helps
An expansion idea can stall when someone has to search for language codes before documenting next steps.
- Looks up codes for the target languages in new ideas.
- Helps language exploration begin with an accurate reference.
- Keeps early expansion work moving.
Setup
Build it in a few focused steps.
- 1Connect Notion and Autom to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give one instruction to use Autom Google Languages to find supported codes for target languages named in each new expansion idea page.
- 4Select the Notion New Page trigger and choose where run reports should go.
- 5Test with one real idea naming a target language.
Questions about this workflow
Can one page name more than one language?
The instruction can ask Autom to return codes for each language named in the new page.
Does the lookup prove that Google supports a country's market?
No. It returns supported Google language codes, which is a different check from country support.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Autom. A trigger fires from one place; an action lands in another.
Notion triggers
Autom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Google Countries
Tool to list google-supported countries. use when you need to filter or suggest countries based on a search string.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Google Images
Tool to fetch images from google search results. use when you need urls, titles, domains, and metadata for images matching a query.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
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.
Google Locations
Tool to retrieve google-supported locations. use when searching for locations by name. returns locations ordered by reach (most populous first).
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 Autom, 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 Autom.