List Webvizio webhooks for new repository commits
Make every push a small opportunity to keep feedback routing from drifting out of sight.
Trigger
Commit Event
Triggered when a new commit is pushed to a repository.
Action
List webhook subscriptions
Tool to list all configured outgoing webhook subscriptions. use when you need an overview of active webhooks before managing them.
Why this helps
Quick commits can accumulate while the configuration that supports visual review becomes invisible.
- Creates a regular configuration pulse
- Keeps feedback setup visible during active coding
Setup
Build it in a few focused steps.
- 1Connect GitHub and Webvizio to Notis once.
- 2Create an automation in the portal.
- 3Describe that Notis should list Webvizio webhook subscriptions for each new GitHub commit event.
- 4Select Commit Event and choose a run-report channel.
- 5Push a test commit to verify it.
Questions about this workflow
Is this suitable for busy repositories?
Choose a reporting channel that keeps frequent run reports manageable for your team.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Webvizio. A trigger fires from one place; an action lands in another.
GitHub triggers
Webvizio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List webhook subscriptions
Tool to list all configured outgoing webhook subscriptions. use when you need an overview of active webhooks before managing them.
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 Webvizio, 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 Webvizio.