Skip to content
Notis

Track the behavior around every new release download

When a binary, archive, or checksum file is added to a GitHub release, Notis exports Clarity data for the website journey that leads users to it.

Trigger

New GitHub Release Asset Added

Triggers when a new asset is added to a specific GitHub release. Monitors a single release (identified by release ID) for newly uploaded assets such as binaries, archives, or checksum files. One event is emitted per new asset, containing full asset metadata.

Action

Data Export

Export data from microsoft clarity.

Why this helps

Download assets are published as an engineering step, while the website journey that drives discovery and conversion is reviewed separately or not at all.

  • Connects artifact publication to the customer journey
  • Supports repeatable download-funnel reviews
  • Avoids a separate analytics handoff

Setup

Build it in a few focused steps.

  • 1Connect the GitHub repository and Microsoft Clarity project to Notis.
  • 2Create a plain-language automation that exports Clarity data whenever a new asset is added to the selected release.
  • 3Pick New GitHub Release Asset Added and your preferred reporting channel.
  • 4Upload one test asset to verify the run.

Questions about this workflow

Does this work for checksums and archives?

Yes. The GitHub trigger detects newly uploaded release assets such as binaries, archives, and checksum files.

Can it monitor all releases?

This event monitors a selected release ID, making it best suited to a specific active launch.

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.