Review Voice Choices After a Drive Edit
When a script changes, make the voice choice easy to revisit with a fresh list of available Aivoov voices.
Trigger
File Updated
Triggers when a file's metadata or content changes in Google Drive.
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
Edits can change a script's tone, but voice options are easy to forget to revisit when work spans multiple tools.
- Make voice selection part of the script update routine.
- Get a current list of available Aivoov voices after a file change.
- Keep voiceover review moving without a separate catalog check.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Aivoov once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis: When a Drive file is updated, list the available Aivoov voices so I can review voice choices for the changed material.
- 4Choose the Google Drive File Updated trigger and select where run reports should go.
- 5Test with one real file update and confirm the run report provides useful voice options.
Questions about this workflow
What counts as an update?
The trigger covers changes to file metadata or content in Google Drive.
Can the workflow tell which words changed?
The trigger description does not say that a before-and-after text comparison is provided. Supply that context if your review instruction requires it.
Does the action generate audio from the updated file?
No. The Aivoov action listed here retrieves available voices only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Aivoov. A trigger fires from one place; an action lands in another.
Google Drive 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.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive 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.