Give short-link review a regular time
A weekly report of recent Cutt.ly links can make link housekeeping easier to return to, even during busy weeks.
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
Without a predictable review time, short-link follow-up can keep slipping behind urgent work.
- Create a regular cue for reviewing recent links.
- Reduce the mental load of remembering a separate link check.
- Choose a cadence and reporting channel that suit your work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cutt.ly to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to set up a recurring link review.
- 3Write one plain-language instruction asking for a report of recent Cutt.ly links.
- 4Select a recurring schedule and choose the channel for run reports.
- 5Run or wait for the first scheduled report, then review it.
Questions about this workflow
Does this require a Notion event?
No. This workflow uses a Notis recurring schedule as its trigger.
Will the weekly report contain every link in my account?
Not necessarily. The action may not return all historical URLs; use the Cutt.ly dashboard for complete history.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cutt ly. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.