Keep bug follow-ups attached to an owner
When a bug is discussed in a meeting, carry the named follow-up owner onto its existing GitHub issue.
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
Bug follow-ups can be discussed clearly and still sit unowned after everyone leaves the call.
- Put named owners on bug issues promptly.
- Keep follow-up tied to the existing issue record.
- Reduce the mental load of tracking ownership across meeting notes and GitHub.
Setup
Build it in a few focused steps.
- 1Connect Avoma and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to assign existing bug issues to owners named in the recap.
- 4Pick the notis_webhook trigger and choose where run reports go.
- 5Test with one real meeting recap that names a bug, its issue, and its owner.
Questions about this workflow
Does it work with bugs that have no GitHub issue yet?
The action applies to an existing issue. A bug without an issue needs to be tracked in GitHub before it can be assigned.
Can it change issue status?
This workflow uses the add-assignees action. It does not change issue status.
What if the recap mentions multiple owners?
Describe in the instruction how to handle multiple named owners, and test with a real example.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Avoma to GitHub. A trigger fires from one place; an action lands in another.
Avoma 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.
Avoma 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.