Validate release completeness automatically
When new assets are added to a GitHub release, Notis queries the full asset list in your calendar so you can verify all expected files are present before announcing the release.
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
List Events
Returns events on the specified calendar.
Why this helps
You publish a release but skip an asset or upload the wrong file. Users download incomplete software. Support tickets pile up. Hours later you realize the problem and have to rerelease and retract announcements. A validation step would have caught it immediately.
- Catch missing or incorrect release assets before users download them
- Reduce support load from incomplete releases by validating before announcement
- Keep release quality high by having a calendar prompt to validate assets
Setup
Build it in a few focused steps.
- 1Connect GitHub and Google Calendar to Notis
- 2Ask Notis: 'When a release asset is added, list all assets so I can validate the release is complete' or set it up in Automations
- 3This creates a calendar entry with the full asset list for easy reference
- 4Choose your notification channel for validation alerts
- 5Upload a test asset to a release and confirm the asset list appears in your calendar entry
Questions about this workflow
What assets should I expect for each release?
Tell Notis what you normally release (binaries, checksums, docs, etc.) and it can alert you if anything is missing.
Can I automate the validation?
Notis will list the assets for you to manually verify. For complex validation, you can add scripts that Notis calls before marking it complete.
Should my release team get the asset list too?
Yes. You can include QA or release managers so everyone validates before announcement.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Google Calendar. A trigger fires from one place; an action lands in another.
GitHub triggers
Google Calendar 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.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
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.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
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.
Update Calendar
Updates metadata for a calendar.
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.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
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 Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
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.
Delete event
Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.
Commit Event
Triggered when a new commit is pushed to a repository.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just GitHub and Google Calendar. 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 Google Calendar.