Keep stale product feedback visible
A small recurring sweep can surface the feedback that is easiest to forget.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Important feedback becomes invisible as newer requests crowd the issue tracker.
- Create a reliable review queue
- Reduce issue-tracker clutter
- Protect valuable customer insight
Setup
Build it in a few focused steps.
- 1Connect Nango and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for it conversationally.
- 3In one instruction, tell Notis to add an appropriate label to product feedback that has had no meaningful activity for the chosen period.
- 4Pick a recurring schedule, select a report channel, and test with one known stale issue.
Questions about this workflow
Can I choose the review cadence?
Yes. Select a recurring schedule such as daily or weekly when creating the automation.
Will existing labels be removed?
No. The GitHub action adds the requested labels without requiring a field-mapping screen.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Nango to GitHub. A trigger fires from one place; an action lands in another.
Nango triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Nango and GitHub. Any 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.