Skip to content
Notis

Pair failed journey checks with real behavior data

When the selected GitHub check concludes unsuccessfully, Notis exports Clarity data so the team can compare automated failure signals with actual user behavior.

Trigger

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.

Action

Data Export

Export data from microsoft clarity.

Why this helps

An end-to-end test failure can launch a long technical investigation before anyone checks whether real users are encountering the same friction.

  • Balances synthetic checks with real behavior signals
  • Creates a faster route to impact evidence
  • Keeps QA investigation focused

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Microsoft Clarity to Notis.
  • 2Ask Notis to export Clarity data when the named user-journey check run fails, times out, or needs action.
  • 3Select Check Run Status / Conclusion Changed and choose the run-report channel.
  • 4Use one safe failing check to test the automation.

Questions about this workflow

Can this monitor one specific check?

Yes. This GitHub event is designed to follow a single configured check run.

Can neutral or skipped conclusions be excluded?

Yes. List only the conclusions that should cause a Clarity export in the prompt.

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.