Catch endpoint regressions close to the commit
Get an outside-in signal while the change is still fresh in your mind.
Trigger
Commit Event
Triggered when a new commit is pushed to a repository.
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
Small commits can quietly affect DNS, routing, or response time, but manual checks are easy to postpone.
- Shortens feedback loops
- Protects focus after shipping changes
- Finds regressions before escalation
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: After each commit to the monitored GitHub branch, run a Globalping measurement against the public endpoint and report meaningful latency or reachability regressions.
- 4Pick the commit event trigger, choose a channel for run reports, and test with one real commit.
Questions about this workflow
Should I monitor every branch?
Start with the production or release branch to keep reports useful and manageable.
Can it ignore documentation commits?
Yes. Include a plain-language condition to skip commits that cannot affect the endpoint.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Measurement
Tool to create and trigger a network measurement. Use when you need connectivity checks from specific geographic or network locations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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.
GlobalPing Health Check
Tool to check API health status. Use when verifying API availability.
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.
List Probes
Tool to list all currently connected probes. Use after authenticating with the API to retrieve online probe metadata.
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 Globalping, 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 Globalping.