Check a requested language before planning
Capture a localization idea in Notion and let Notis check Amara's supported language options.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Available Languages
Tool to get a list of all supported languages. use when you need to know available language options from amara.
Why this helps
Planning around an unsupported language option can create avoidable rework and an awkward late-stage discovery.
- Provides a current supported-language list for checking.
- Catches language availability concerns early.
- Reduces rework in localization planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Amara to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one plain-language instruction, ask Notis to check the requested language in Amara's supported-language list when a new localization plan is created and report the result.
- 4Choose the Notion New Page trigger and select a channel for run reports.
- 5Test with a plan that names a real requested language.
Questions about this workflow
Does this create a language track?
No. It checks the available language options; creating a subtitle language is a separate action.
What should the plan include?
Include the requested language in a clear form so Notis can compare it to Amara's supported options.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Amara. A trigger fires from one place; an action lands in another.
Notion triggers
Amara actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Subtitle Note
Tool to add a note to a subtitle set. use after retrieving the notes uri of the subtitle set.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Subtitle Language
Tool to create a new subtitle language for a video. use when you need to add a language track (iso 639-1 code) before uploading subtitles.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fetch Subtitles Data
Tool to fetch subtitle data for a video in a specific language. use when you need to retrieve subtitle segments after confirming video id and language code.
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.
Get Subtitle Language Details
Tool to retrieve details for a single subtitle language. use when you have video id and language code and need metadata about that language track.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Team Details
Tool to get details on a specific team by slug. use when you need metadata for a single team.
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.
Get User Data
Tool to get user data by username or id. use when you need to fetch account details for a user.
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.
Get Video URL Details
Tool to get details for a specific video url. use when you have a public or embeddable video url and need its amara metadata (id, title, duration, thumbnails, etc.).
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.
List Available Languages
Tool to get a list of all supported languages. use when you need to know available language options from amara.
Connect any two apps with Notis in the middle.
Notion and Amara, 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 Amara.