Put customer impact on the bug issue
Send the customer report and its linked GitHub issue details to Notis so the issue carries a customer-impact label.
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
Engineering teams may see the technical bug while missing how many customers or accounts it affects.
- Make customer impact visible in issue triage.
- Keep account context close to the technical work.
- Let the team prioritize from the information supplied in the report.
Setup
Build it in a few focused steps.
- 1Connect Agiled and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer-impact triage.
- 3Tell Notis to add the customer-impact label to the GitHub issue identified in the request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real bug report that includes a repository, issue number, and impact context.
Questions about this workflow
Can Notis calculate how many customers are affected?
Only if the request supplies that information. Notis can interpret returned or provided data, but it cannot create a missing customer count or impact baseline.
Does GitHub need the label to exist already?
The listed GitHub action creates labels that do not already exist, so the requested label can be added to the issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agiled to GitHub. A trigger fires from one place; an action lands in another.
Agiled 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.
Agiled 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.