Deepen Reflection With Audio-Guided Prompts - Voices Ready
Reflection sticks better when prompted aloud. When you add a reflection prompt to Notion, Notis shows you calm, guiding voices to read it during your practice.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
List Voices
Tool to retrieve a list of available voices. use to filter voices by language after confirming api key is valid.
Why this helps
Neurodivergent founders struggle with solo reflection without external structure. Prompts sitting on a page don't engage the same as audio guidance.
- Calm voices ready for reflection practice
- Audio engagement deeper than reading
- Build consistency in reflection habit
- Support mental clarity and growth
Setup
Build it in a few focused steps.
- 1Connect your Notion journal and Aivoov to Notis
- 2Ask Notis 'When I add a reflection prompt to my journal in Notion, show me calm, guiding voices to read it during reflection'
- 3Choose your notification channel for gentle reminders
- 4Add a test reflection prompt to Notion and verify soothing voice options arrive for guided practice
Questions about this workflow
What makes a voice good for reflection?
Slow pacing, warm tone, no urgency. Reflection voices should feel like a trusted guide, not a narrator rushing you through.
Can I use the same voice every day or should I vary?
Variety keeps it fresh. Some days pick a warm voice, other days a more neutral guide. Let Notis show you options and choose what lands.
How long should reflection practice be?
This is up to you. Notis shows voices that work for 5 minutes or 30 minutes of reflection. You set the pace.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Aivoov. A trigger fires from one place; an action lands in another.
Notion triggers
Aivoov actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Voices
Tool to retrieve a list of available voices. use to filter voices by language after confirming api key is valid.
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 Aivoov, 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 Aivoov.