Keep campaign links visible in weekly planning
A small, recurring checkpoint can keep campaign links from becoming another thing to remember later.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Campaign execution often spreads across issues and link tools, leaving owners to connect the dots manually.
- Connects a scheduled link scan with campaign-related Linear work for review.
- Provides one consistent place to notice possible link follow-ups.
Setup
Build it in a few focused steps.
- 1Connect Linear and Cutt ly to Notis once through the portal.
- 2Ask Notis to retrieve recent Cutt ly URLs on a chosen weekday and summarize visible Linear campaign work that may need a link check.
- 3Create the automation with a weekly schedule and choose a channel for run reports.
- 4Test one run against a real campaign week.
Questions about this workflow
Can the schedule fit our campaign cadence?
Yes. Choose a recurring weekly schedule that matches your planning rhythm.
Will every recent link be campaign-related?
No. The owner should review the recent URL list and the Linear summary to confirm relevance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Cutt ly. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.