Keep Share Links Close to Pull Request Review
A new pull request can be the cue to check your latest shortened links. Notis gathers recent Cutt ly URLs into the run report while the change is fresh.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
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
When code review starts, related preview or release links can be buried in a separate dashboard or forgotten until someone asks for them.
- See recent shortened URLs when a PR enters review.
- Keep link checks in the same follow-up moment as code review.
- Use the report to identify links that may need a human check.
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 recently shortened Cutt ly links when a pull request is created and include them in the run report for review.
- 4Pick the GitHub New Pull Request Created trigger and choose where run reports go.
- 5Test with one real pull request; the returned Cutt ly list may not include full link history.
Questions about this workflow
Can it tell which Cutt ly link belongs to the pull request?
The listed action returns recent shortened URLs, but does not specify a search or matching capability. Ask Notis to present the returned links for review rather than assume a match.
Can I filter this trigger to a particular repository or branch?
The GitHub event supports optional filters, but Notis setup is prompt-based and users do not build filters in setup. Select the event and describe the desired outcome in plain language.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
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.