Route support transcript bugs to an owner
When a support call ends with a clear engineering commitment, put that owner on the GitHub issue tracking the bug.
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
Support bugs can move between teams without anyone owning the engineering follow-up in GitHub.
- Connects a support report to an accountable issue owner.
- Keeps the original support context available for engineering follow-up.
- Avoids routing based on assumptions about team roles.
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 match support transcript bug reports to existing GitHub issues and assign only the named person who explicitly accepts ownership and can be assigned.
- 4Choose a webhook trigger and the channel for run reports.
- 5Test with one support transcript and verify the matched issue and owner.
Questions about this workflow
Does it create an issue from a new support bug?
No. This workflow uses the GitHub add assignees action on an existing issue.
What if the support transcript contains no owner?
Notis should leave the issue unassigned and report that ownership needs confirmation.
Can it assign someone who is not assignable to the repository?
No. The instruction requires a person who can be assigned to the 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.