Pair New Assets With the Right Paperwork
A new download, build, or package can create follow-up work. Notis helps you see the document side immediately.
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 Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Why this helps
Supporting forms and agreements can be forgotten when a release asset is uploaded separately from the launch plan.
- Review supporting documents at asset upload time.
- Reduce missed distribution follow-up.
- Keep customer-facing launches coordinated.
- Make small release steps easier to remember.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Boloforms to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use this instruction: When a new GitHub release asset is added, retrieve the Boloforms document list and summarize customer-facing documents relevant to the asset.
- 4Pick the release-asset trigger, choose a report channel, and test with one uploaded asset.
Questions about this workflow
Can it focus on a specific release?
Yes. Configure the GitHub trigger for the release you want to monitor.
What counts as a relevant document?
Ask Notis to focus on download terms, customer forms, partner agreements, or distribution paperwork.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Boloforms. A trigger fires from one place; an action lands in another.
GitHub triggers
Boloforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Boloforms, 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 Boloforms.