Turn Canny bug reports into clearly labeled GitHub issues
When Canny feedback points to an existing GitHub issue, Notis can add a bug label so it is easier to spot and triage.
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
Bug reports can sit in feedback queues without a clear signal on the GitHub issue that needs attention.
- Make matching bug reports easier to find in GitHub.
- Avoid labeling issues when feedback does not identify a clear match.
- Reduce manual checks between feedback and issue tracking.
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 add the bug label to an existing GitHub issue only when incoming Canny feedback clearly identifies that issue; specify the label name in your instruction.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real Canny report that links to an existing GitHub issue.
Questions about this workflow
Does this create a GitHub issue?
No. The available GitHub action adds labels to an existing issue. The feedback must identify an issue that Notis can match.
Can I choose the label?
Yes. Name the label in your instruction. GitHub creates the label if it does not already exist.
What if the feedback does not identify an issue?
Tell Notis to skip it and report that it could not find a clear match.
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.