Skip to content
Notis

Add user-impact evidence to failed workflow triage

Notis responds to a failed GitHub workflow run with a Clarity export, helping you assess whether the technical failure coincides with visible customer friction.

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

Data Export

Export data from microsoft clarity.

Why this helps

A failing production workflow creates urgency, but the user-impact check becomes a separate task that is easy to overlook.

  • Adds customer-behavior context to technical triage
  • Reduces the number of manual incident checks
  • Helps separate noisy failures from visible impact

Setup

Build it in a few focused steps.

  • 1Connect the relevant GitHub repository and Microsoft Clarity project to Notis.
  • 2Describe one automation that exports Clarity data when the production workflow concludes with failure or timeout.
  • 3Choose GitHub Workflow Run State Changed and a channel for incident run reports.
  • 4Test with a safe failed workflow run.

Questions about this workflow

Can successful workflow runs be ignored?

Yes. State the allowed failure conclusions in the plain-language prompt.

Does the export fix the failed workflow?

No. It supplies behavior data to support impact assessment while your existing recovery process handles the failure.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Microsoft clarity. A trigger fires from one place; an action lands in another.

GitHub triggers

Microsoft clarity actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Data Export

Export data from microsoft clarity.

ActionInstant

Webhook trigger

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

TriggerInstant

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

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

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

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 Microsoft clarity, 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 Microsoft clarity.