Find an available Aivoov voice for the language in your GitHub task
When a new GitHub issue requests a voiceover in a specific language, Notis can retrieve Aivoov voices available for that language and return the options with the task context. The workflow helps you choose a voice; it does not generate audio.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
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
Finding the right language support can become a separate research step when preparing accessible or localized release materials.
- Start voice discovery from a clearly labeled GitHub request.
- Filter the available Aivoov voices using the language specified in the issue.
- Keep voice selection separate from audio generation so a person can review options before production.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Aivoov to Notis once, and confirm the Aivoov API connection is valid.
- 2Create an automation in the portal or ask Notis conversationally; instruct it to list Aivoov voices for the requested language only when a new issue uses your voiceover-localization label.
- 3Select the new issue trigger, filter for that label, and choose a channel for run reports.
- 4Test with one issue that names a target language and verify the listed voices match it.
Questions about this workflow
Will this create the voiceover audio?
No. The available action only lists voices and can filter by language. It does not create or deliver audio.
What should the GitHub issue include?
State the target language and that the task is a voiceover or localization request. The workflow returns the available voice options for someone to review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Aivoov. A trigger fires from one place; an action lands in another.
GitHub 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.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub 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.