Put release follow-ups on the right GitHub owner
Capture clear commitments from release discussions and attach them to the issues that need follow-through.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Release tasks often leave a meeting without a clear owner in GitHub, so blockers linger until someone chases them.
- Records explicit release follow-up ownership.
- Keeps the issue tied to the release discussion that created the commitment.
- Leaves unclear or unassignable owners for review.
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 find release follow-ups and matching GitHub issues, then add an assignee only when a named person explicitly accepts the task and can be assigned.
- 4Choose a webhook trigger and the channel for run reports.
- 5Test with one transcript containing a named commitment and a known issue.
Questions about this workflow
Will it infer who owns a task from their role?
No. It should only use an explicit commitment and a confirmed assignable person.
Can this create the missing issue?
No. This package uses the add assignees action on an existing issue.
What if a follow-up has no issue yet?
The run report can surface it for a person to create or identify the appropriate issue.
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.