Prepare Meeting Audio Before Your Notes Are Even Done
Meeting preparation shouldn't require five context switches. Create your meeting notes in Notion and immediately see what voices are ready to record your agenda or follow-up.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
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
ADHD founders lose energy preparing meetings. Switching between Notion notes and Aivoov for voice selection breaks planning momentum and meetings end up under-prepared.
- Voices ready before your meeting notes are finalized
- Record agendas and follow-ups in your own voice or professional narration
- No tool-switching during prep
- Show up to meetings more prepared and present
Setup
Build it in a few focused steps.
- 1Connect Notion and Aivoov to Notis (one-time setup in the portal)
- 2Create an automation by asking Notis 'When I add meeting notes to Notion, show me available voices for recording agenda audio' or use the portal
- 3Pick your notification channel (Slack works great for meeting prep reminders)
- 4Create a test meeting note in Notion and check that Notis sends available voice options
Questions about this workflow
Can I use this for one-on-ones or only team meetings?
Both. Any meeting type counts. Whether it's a standup, board meeting, or coaching call, Notis retrieves voices when you create the notes.
What do I do with the voice list Notis sends?
Pick a voice from Aivoov that matches your meeting's tone (professional, casual, energetic). Then narrate your agenda or key points for better retention.
Does this work if I already have meeting notes in Notion?
This triggers when new meeting notes are created. For existing notes, you can manually check voices once, but the automation works automatically going forward.
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.