Skip to content
Notis

Bring recent links into focused page discussions

When a specified Notion page gets a new comment, receive a recent Cutt.ly link report as a lightweight discussion follow-up.

Trigger

New Comment

Triggers when a new comment is added to a specified Notion block or page.

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 a discussion is anchored to one key page, remembering to check a separate link list adds unnecessary mental overhead.

  • Keep the trigger tied to a specified discussion page or block.
  • Give collaborators a recent-link report when discussion begins.
  • Avoid searching for a separate link list mid-conversation.

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 tell Notis the discussion follow-up you want.
  • 3Give Notis one plain-language instruction to retrieve recent Cutt.ly links when a comment is added to the chosen page or block.
  • 4Choose Notion New Comment, specify the page or block in the trigger, and choose a report channel.
  • 5Add a test comment there and review the report.

Questions about this workflow

How is this different from the workspace comment trigger?

New Comment is for a specified Notion block or page, while Comment Created can be workspace-wide or scoped to a page.

Can it list the full Cutt.ly history?

No. The action may return recent links only; Cutt.ly's dashboard is recommended 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.

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

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.