Give confirmed transcript follow-ups an owner
A recurring review can catch clear commitments that still have no assignee on their GitHub issue.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Some follow-ups are discussed after an issue is created, and the task remains unassigned even though the call settled who owns it.
- Focuses on existing issues that remain unassigned.
- Uses only owners explicitly named in transcript material.
- Creates a repeatable path for overlooked commitments.
Setup
Build it in a few focused steps.
- 1Connect AssemblyAI and GitHub once in the Notis portal.
- 2Create an automation in Automations, then choose New Automation.
- 3Tell Notis to review available transcript material, find matching unassigned GitHub issues, and assign only an explicitly committed, assignable owner.
- 4Choose a recurring schedule and the channel for run reports.
- 5Test with one real transcript and a matching unassigned issue.
Questions about this workflow
Does this scan every AssemblyAI recording automatically?
No. No AssemblyAI trigger or transcript retrieval action is listed. Notis can use transcript material available to it.
Will it replace an existing owner?
The instruction is limited to unassigned issues, so it should leave issues with an assignee unchanged.
What happens if two people appear to own the task?
Notis should not choose between them without a clear commitment. It can report the issue for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AssemblyAI to GitHub. A trigger fires from one place; an action lands in another.
AssemblyAI triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
AssemblyAI and GitHub, 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 GitHub.