Bring current Lmnt voice options into a new selection view
Make a new comparison space useful with the current available voice list.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Get Voices List
Gets a list of voices in lmnt.
Why this helps
A new selection view is less useful when its voice options still need to be found in another tool.
- Start a new selection space with current options available.
- Reduce the extra lookup step before comparing voices.
- Keep voice exploration moving while attention is on the new view.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lmnt to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to fetch voice options for a new selection view.
- 3Write one plain-language prompt asking Notis to retrieve the current Lmnt voice list when a relevant selection view is created.
- 4Select the Notion View Created trigger and choose a channel for run reports.
- 5Test by creating one real voice selection view.
Questions about this workflow
Will this run for all new views?
The View Created trigger is workspace-wide, so ask Notis to check whether the new view is for voice selection before retrieving the list.
Does it create a comparison automatically?
This action retrieves the available voices. Use the plain-language prompt to ask for a concise comparison summary if useful.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lmnt. A trigger fires from one place; an action lands in another.
Notion triggers
Lmnt actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Voice
Creates a voice in lmnt.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Voice Info
Deletes information about a specific voice in lmnt.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Account
Gets an account in lmnt.
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 Voice Info
Gets information about a specific voice in lmnt.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Voices List
Gets a list of voices in lmnt.
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 Synthesize Speech
Synthesizes speech from text using a specific voice in lmnt.
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.
Update Voice Info
Updates information about a specific voice in lmnt.
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 Lmnt, 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 Lmnt.