Keep downloadable release updates current
When the file is ready, the customer-facing update should be easy to verify too.
Trigger
New GitHub Release Asset Added
Triggers when a new asset is added to a specific GitHub release. Monitors a single release (identified by release ID) for newly uploaded assets such as binaries, archives, or checksum files. One event is emitted per new asset, containing full asset metadata.
Action
Get Posts
Tool to retrieve a list of posts. use when you need ids and titles of posts for further operations.
Why this helps
A release asset may become available while the Beamer update still lacks the correct download or availability context.
- Catch communication gaps when assets are uploaded.
- Reduce manual release-page checking.
- Keep availability messaging timely.
- Support smoother handoffs between building and announcing.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Beamer to Notis once through the portal.
- 2Create the automation with a plain-language instruction to retrieve related Beamer posts.
- 3Choose the new GitHub release asset trigger.
- 4Select a reporting channel and test with one uploaded asset.
Questions about this workflow
What kinds of assets are covered?
The trigger covers newly uploaded release assets such as archives, binaries, and checksum files.
Does this replace release QA?
No. It provides a focused Beamer communication checkpoint alongside your normal QA.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Beamer. A trigger fires from one place; an action lands in another.
GitHub triggers
Beamer 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.
Count Posts
Tool to count existing posts. use when you need the number of posts matching specific filters.
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.
Get Category
Tool to retrieve a specific category by its id. use when you need to load metadata for a category before filtering or grouping posts by that category.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Feed
Tool to retrieve the url for your standalone feed. use after embedding to fetch the feed link for embedding or sharing.
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.
Get Feeds
Tool to retrieve the url for your feed. use when you need to embed or access your standalone feed.
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.
Get Feed URL
Tool to retrieve the url for your personalized feed. use after setting segmentation or language options to embed or redirect users.
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.
Get Notification
Tool to retrieve details of a specific notification by its unique notification id. use after obtaining the notification id to fetch its full details.
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.
Get Notifications
Tool to fetch unread notifications. use after providing user context to retrieve and mark notifications as read.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Post Comments
Tool to retrieve comments for a specific post. use after identifying the post id to list its comments.
Connect any two apps with Notis in the middle.
Not just GitHub and Beamer. 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 Beamer.