Keep customer requests visible in GitHub
Bring customer context into the issue list by tagging work that a transcript explicitly identifies as a customer request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Customer needs may be discussed in calls but disappear from engineering triage when the issue carries no signal about who needs it.
- Preserves customer context alongside tracked work.
- Helps triage teams find customer-requested issues.
- Requires clear evidence before applying a label.
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 identify customer requests stated in the transcript, match them to existing GitHub issues, and add a customer request label only when the link is clear.
- 4Choose a webhook trigger and the channel for run reports.
- 5Test with one transcript containing an explicit customer request and a known issue.
Questions about this workflow
Can Notis tell which requests came from a customer?
Only if the transcript or supplied context identifies the speaker or request as customer input. Notis should not infer that from missing information.
Does this create new issues?
No. This workflow adds labels to matching existing issues.
What if one request relates to several issues?
Notis should label only issues with a supported match and report uncertainty 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.