Keep iterative PR changes connected to live behavior
Every new PR commit can change the customer experience. Check the signals before the thread goes cold.
Trigger
New Commit Added to Pull Request
Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.
Action
List notifications
Tool to list account notifications. use after authenticating to retrieve notifications for one or all wachets within an optional time range.
Why this helps
Follow-up commits can accumulate while no one remembers to revisit affected live pages or monitors.
- Creates a lightweight review cue for each new commit
- Helps catch repeated regressions earlier
- Reduces manual monitoring checks during iteration
Setup
Build it in a few focused steps.
- 1Connect GitHub and Wachete to Notis once through the portal.
- 2Create an automation and tell Notis: When a new commit is added to the selected GitHub pull request, list recent Wachete notifications and summarize possible regressions.
- 3Select the new-PR-commit trigger, choose the reporting channel, and test with one commit.
Questions about this workflow
Will it run for force-pushed commits?
Yes. The GitHub trigger covers newly added commits on the monitored pull request, including force-pushes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Wachete. A trigger fires from one place; an action lands in another.
GitHub triggers
Wachete actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Watcher
Tool to create a new watcher. use when setting up page monitoring after specifying url and xpath. confirm page url and xpath validity before running.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete watcher
Tool to delete a watcher. use when you need to remove a monitor by its id after confirmation. confirm the watcher id is correct before calling. example: "delete watcher with id 123abc."
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.
Get folder content
Tool to retrieve the content of a folder. use when you need to list subfolders and watchers inside a specific folder after managing folder structure.
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 notifications
Tool to list account notifications. use after authenticating to retrieve notifications for one or all wachets within an optional time range.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List watchers
Tool to list all watchers. use when you need to retrieve your configured monitoring tasks.
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 Wachete, 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 Wachete.