Keep Canny feature details current from GitHub README updates
Avoid maintaining the same explanation in two places.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Update Post
Tool to update post details. use when you need to change a post's title, details, eta, images, or custom fields.
Why this helps
Feature descriptions drift when documentation and feedback posts are edited separately.
- Fewer stale descriptions
- One source of truth
- Reduced editing effort
Setup
Build it in a few focused steps.
- 1Connect GitHub and Canny to Notis once.
- 2Create an automation instructing Notis to refresh the linked Canny post details when the relevant README changes.
- 3Pick GitHub Repository README Changed, choose a report channel, and test with a small documentation edit.
Questions about this workflow
Can it preserve the feedback discussion?
Yes, ask Notis to update only the feature details, not comments or votes.
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.