Bring customer call themes into issue triage
Let Notis turn customer problems captured in Avoma into labels on the GitHub issues already tracking them.
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 feedback gets lost between call notes and engineering triage, so related issues are harder to recognize.
- Make customer themes easier to spot during issue review.
- Connect call evidence to existing engineering work.
- Cut down on manual recap-to-issue cleanup.
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 label existing issues that match customer themes in call notes.
- 4Pick the notis_webhook trigger and choose where run reports go.
- 5Test with one real customer-call recap and review the selected issue and labels.
Questions about this workflow
Does this create an issue for every customer request?
No. The selected GitHub action adds labels to an existing issue. The recap should include context that helps identify it.
Can it distinguish a request from a bug report?
Notis can interpret the recap, but your instruction should state how to label each type.
What if there is no matching issue?
The action needs an existing issue. Review the run report and provide an issue reference or adjust the prompt before trying again.
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.