Skip to content
Notis

Bring Recent Short Links Into Workflow Run Follow-Up

A workflow run changing state is a useful checkpoint. Notis can retrieve recent Cutt ly links so you can decide whether any need a post-run review.

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

View Last Shortened URLs

This action retrieves a list of recently shortened urls from your cutt.ly account. it allows users to view their latest shortened links and their details. note: due to api limitations, this action may not return all historical urls. for complete history, please use the cutt.ly dashboard.

Why this helps

Run outcomes and shortened links are checked in different places, which can leave a necessary link review until later or missed entirely.

  • Tie a recent-link check to a workflow state change.
  • See Cutt ly results in the run report channel you choose.
  • Make post-run link follow-up easier to remember.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Cutt ly once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis from any channel.
  • 3In one instruction, ask Notis to retrieve recent Cutt ly URLs when the monitored workflow run changes state and summarize them for post-run review.
  • 4Pick the GitHub Workflow Run State Changed trigger and choose where run reports go.
  • 5Test with one real workflow run state change and inspect the report.

Questions about this workflow

Can this action report the workflow artifact or deployment URL?

The Cutt ly action retrieves recent shortened URLs. The listed action does not promise to fetch GitHub artifacts, deployment URLs, or a full link history.

Will it run only when a workflow succeeds?

The trigger covers workflow run status or conclusion changes. The setup does not offer user-built filters; describe the intended outcome to Notis and check the behavior with a real example.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

GitHub triggers

Cutt ly actions

Recurring trigger

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

TriggerScheduled

View Last Shortened URLs

This action retrieves a list of recently shortened urls from your cutt.ly account. it allows users to view their latest shortened links and their details. note: due to api limitations, this action may not return all historical urls. for complete history, please use the cutt.ly dashboard.

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 Cutt ly, 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 Cutt ly.