Turn GitHub releases into Canny changelog entries
Reuse release notes instead of rewriting the same launch update.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
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.".
Why this helps
Release notes are written once, then forgotten before customers see them.
- Faster launches
- Consistent messaging
- Less duplicate writing
Setup
Build it in a few focused steps.
- 1Connect GitHub and Canny to Notis once.
- 2Create an automation asking Notis to draft or publish a Canny changelog entry from a published GitHub release.
- 3Pick GitHub Release State Changed, choose a report channel, and test with a draft release.
Questions about this workflow
Can I review before publishing?
Yes, tell Notis to create the changelog entry as a draft.
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
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.
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.
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.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 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.".
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 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.
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 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"
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Canny. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Canny.