Check Available Voices When a Notion Item Changes
When a production item's status changes, get a fresh list of available ElevenLabs voices to support the next voice decision.
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
List Voices
List the ElevenLabs voices available to this account (voice_id, name, category, labels, preview_url).
Why this helps
Looking up voice options in a separate tool can slow down a production decision.
- Bring voice options into a status-driven production routine.
- Avoid repeated manual checks for the available voice roster.
- Give the next review step a timely starting point.
Setup
Build it in a few focused steps.
- 1Connect Notion and ElevenLabs to Notis once through the portal.
- 2Create an automation prompt asking Notis to list available ElevenLabs voices when a production item's properties change.
- 3Select the Notion Page Properties Updated trigger and scope it to the production data source if appropriate.
- 4Choose a channel for run reports and test by changing a relevant item's property.
Questions about this workflow
Does this choose a voice automatically?
No. It lists voices available to the account so you can make the selection.
Can I limit which property updates matter?
Describe the relevant status change in the plain-language prompt. The trigger itself can be scoped to a data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to ElevenLabs. A trigger fires from one place; an action lands in another.
Notion triggers
ElevenLabs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Voice Isolator
Remove background noise, music and ambient sounds from a recording, returning clean studio-quality speech (MP3, base64).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Voice Changer
Transform a recording into a different ElevenLabs voice while preserving the original emotion, timing and delivery (MP3, base64 output).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Forced Alignment
Align a known transcript to its audio recording, returning precise word-level timestamps (subtitles, audiobook timings, karaoke).
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 Voices
List the ElevenLabs voices available to this account (voice_id, name, category, labels, preview_url).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Speech to Text
Transcribe an audio or video file from a URL with ElevenLabs Scribe — 90+ languages, word timestamps, speaker diarization, audio-event tagging, optional entity detection and keyterm biasing.
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.
Music Generation
Generate studio-grade music (MP3) in any style from a natural language prompt with Eleven Music — vocals or instrumental, commercial-use cleared.
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 ElevenLabs, 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 ElevenLabs.