Keep public documentation changes visible
When your repository narrative changes, make sure the customer-facing documentation surface gets attention too.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
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.
Why this helps
README edits can reflect product changes while related public pages remain unmonitored or stale.
- Connects internal documentation changes to public-page awareness
- Creates monitoring at the moment of change
- Reduces forgotten launch-support tasks
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 the repository README changes, create a Wachete watcher for the related public documentation page at this URL and XPath.
- 3Select the README-change trigger, choose the run-report channel, and test with one real edit.
Questions about this workflow
Is the README itself monitored by Wachete?
The trigger comes from the README change; the action creates a Wachete watcher for the public page you specify.
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
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 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.
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.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 notifications
Tool to list account notifications. use after authenticating to retrieve notifications for one or all wachets within an optional time range.
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.
List watchers
Tool to list all watchers. use when you need to retrieve your configured monitoring tasks.
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 Wachete. 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 Wachete.