Keep release changes tied to production reality
When release information moves, verify that the live product still answers from the network.
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 Measurement
Tool to create and trigger a network measurement. Use when you need connectivity checks from specific geographic or network locations.
Why this helps
Release edits can trigger customer-facing changes without a deliberate production verification step.
- Links release activity to operational confidence
- Reduces forgotten verification steps
- Supports calmer launch communication
Setup
Build it in a few focused steps.
- 1Connect GitHub and Globalping to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Use this instruction: When the monitored GitHub release changes, run a Globalping measurement against production and explain whether reachability or latency changed.
- 4Choose the release state trigger, select a report channel, and test with one real release update.
Questions about this workflow
Which release changes can trigger it?
The GitHub trigger covers release title, notes, draft, prerelease, publication, target, and asset changes.
Is this useful for prereleases?
Yes. Use a staging or prerelease target in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Globalping. A trigger fires from one place; an action lands in another.
GitHub triggers
Globalping 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.
Create Measurement
Tool to create and trigger a network measurement. Use when you need connectivity checks from specific geographic or network locations.
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 Measurement Results
Tool to get measurement results by ID. Use when you need to retrieve the status and detailed per-probe results of an existing measurement.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
GlobalPing Health Check
Tool to check API health status. Use when verifying API availability.
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.
List Probes
Tool to list all currently connected probes. Use after authenticating with the API to retrieve online probe metadata.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Globalping. 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 Globalping.