Skip to content
Notis

Pair automation results with customer-facing signals

When CI or deployment automation finishes, add one concise check of what monitored pages are saying.

Trigger

GitHub Workflow Run State Changed

Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).

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

Workflow results can close one loop while the customer-facing loop remains unchecked.

  • Adds a clear post-run review cue
  • Reduces uncertainty after automation completes
  • Keeps operational signals near engineering outcomes

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 selected GitHub Actions workflow run changes state, list Wachete notifications from the relevant time window and summarize anything that needs attention.
  • 3Pick the workflow-run-state trigger, choose the report channel, and test with one run.

Questions about this workflow

Can it focus on failed runs?

Configure the monitored workflow and tell Notis in the instruction to prioritize failed or otherwise actionable states.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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."

ActionInstant

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.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

List notifications

Tool to list account notifications. use after authenticating to retrieve notifications for one or all wachets within an optional time range.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

List watchers

Tool to list all watchers. use when you need to retrieve your configured monitoring tasks.

ActionInstant

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.