Keep feedback-linked GitHub issues marked for review
A scheduled check can surface feedback that was missed during the day and mark its clearly linked GitHub issue for review.
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
Feedback can be overlooked when the team relies on one-off manual checks across separate tools.
- Catch feedback that may have missed immediate triage.
- Mark only clearly matched existing GitHub issues.
- Keep a run report for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Canny and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to review available Canny feedback since the previous run and add your chosen label only to existing GitHub issues it can clearly match.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real Canny item linked to an existing GitHub issue.
Questions about this workflow
Can Notis know which items are new since the last run?
The instruction can ask Notis to avoid reprocessing prior items, but the available app descriptions do not specify history or a last-run marker. Supply a reliable way to identify unreviewed feedback if needed.
Will this create missing GitHub issues?
No. The available action adds a label to an existing issue.
What should happen if no linked issue is found?
Instruct Notis to skip the item and include the missing match in its run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Canny to GitHub. A trigger fires from one place; an action lands in another.
Canny 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.
Canny 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.