Reference Docs That Developers Love - Audio Format Included
Some neurodivergent developers prefer voice-first learning. When you update API docs in Notion, Notis shows voices to create audio references.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
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 developers with ADHD or dyslexia prefer audio documentation but creating it requires manual tool-switching and setup.
- Audio docs ready when technical content updates
- Support alternative learning styles on the team
- Developers reference docs via listening and reading
- Wider accessibility for technical teams
Setup
Build it in a few focused steps.
- 1Connect your Notion technical docs and Aivoov to Notis
- 2Ask Notis 'When API documentation updates in Notion, show me voices for creating audio references'
- 3Set notifications to your developer team channel
- 4Update a test API doc page in Notion and verify technical documentation voice options arrive
Questions about this workflow
What speed is best for technical audio docs?
Slower than normal speech with clear pronunciation. Technical terms need time to register. Notis shows paced options designed for complexity.
Can I include code samples in audio form?
Sort of. Voice can describe code logic, but developers still need to see actual code. Audio works best for explaining concepts, not reading code line-by-line.
Should I update audio docs every time I update written docs?
Not necessarily. Update audio for major changes or new sections. Minor updates can skip the audio update.
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.