Keep Canny categories in step with GitHub labels
Make prioritization signals easier to see in your feedback space.
Trigger
GitHub Issue Labels Changed
Triggers when the labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored issue. The payload includes: - ``current_labels`` -- the full set of labels currently on the issue - ``added_labels`` -- labels that were newly added - ``removed_label_names`` -- names of labels that were removed - ``changed_label_names`` -- labels whose metadata changed without being added or removed
Action
Add Post Tag
Tool to add a tag to a specific post. use when you need to categorize or group content by applying an existing tag.
Why this helps
Priority cues disappear when product and engineering use different backlogs.
- Consistent signals
- Faster backlog scans
- Less manual categorization
Setup
Build it in a few focused steps.
- 1Connect GitHub and Canny to Notis once.
- 2Create an automation instructing Notis to add the matching Canny tag when a linked issue receives a named priority label.
- 3Pick GitHub Issue Labels Changed, choose a report channel, and test with one labeled issue.
Questions about this workflow
Do I need to map fields?
No, describe the label-to-tag outcome in plain language.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Canny. A trigger fires from one place; an action lands in another.
GitHub triggers
Canny actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Post Tag
Tool to add a tag to a specific post. use when you need to categorize or group content by applying an existing tag.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete User
Tool to delete a user and their comments and votes. use when you need to fully remove a user's account and all associated data (e.g., gdpr compliance).
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Change Post Status
Tool to change a post's status. use when you need to update a post's workflow stage and optionally notify voters.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Create Changelog Entry
Tool to create and optionally publish a new changelog entry. use when you need to add a product update record, control publish timing, and notify users. example: "create changelog entry titled 'version 1.2' with details '...' and publish immediately.".
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Comment
Tool to create a new comment on a post. use when you have the authorid and postid and want to submit feedback or replies.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Create or Update User
Tool to create or update a user in canny. use when you need to provision a new user or synchronize updates to an existing user profile. example: "create or update user with email user@example.com"
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create Post
Tool to create a new post on a board. use when you have the boardid and userid and need to submit new feedback.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Create Tag
Tool to create a new tag. use when you have the boardid and tag name and need to categorize posts.
Connect any two apps with Notis in the middle.
GitHub and Canny, 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 Canny.