Add a Capacity Check to Release Packaging
Release packaging is a useful moment to confirm that your supporting data workflows still have room to run.
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 Usage
Tool to get usage information and remaining credits for your piloterr account. use when you need to check account usage and credit details.
Why this helps
Launch preparation creates many small checks, and usage limits are easy to overlook among them.
- Attach usage monitoring to release activity.
- Reduce launch-day uncertainty.
- Avoid separate account-dashboard checks.
- Make operational readiness easier to verify.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Piloterr to Notis once.
- 2Create the automation in the portal or ask Notis to create it by message.
- 3Use this instruction: When a new asset is added to a GitHub release, check Piloterr usage and report remaining credits and any capacity warning.
- 4Pick the new release asset trigger and choose where Notis reports runs.
- 5Test with one release asset upload.
Questions about this workflow
Can this monitor one release only?
Configure the GitHub trigger for the release that matters to your launch process.
What does Notis report?
It reports current Piloterr usage information and the release asset that triggered the check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Piloterr. A trigger fires from one place; an action lands in another.
GitHub triggers
Piloterr actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Auchan Product
Tool to retrieve detailed auchan product information. use when you have a product id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Auchan Product Search
Tool to search for products on auchan by query or search url. use when you need product listings and details from auchan.
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.
Piloterr Get Product Info
Tool to retrieve detailed product information by product id. use when you need full product details including company info.
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.
Bestbuy Product Search
Tool to search for products on bestbuy by query. use when you need to retrieve bestbuy items by keywords with optional pagination and price filters.
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 Usage
Tool to get usage information and remaining credits for your piloterr account. use when you need to check account usage and credit details.
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 Piloterr, 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 Piloterr.