Connect Spotify to Cutt ly

When something happens in Spotify, Notis takes the next step in Cutt ly. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Spotify to Cutt ly

View example

Check promotion links after a Spotify playlist change

When a Spotify playlist changes, review your latest Cutt ly links and identify promotion links that may need attention.

View example

Create a link digest for playlist changes

After a Spotify playlist item change, retrieve recent Cutt ly links and summarize the links most relevant to the playlist campaign.

View example

Review old short links after playlist changes

Use a Spotify playlist item change to prompt a review of recent Cutt ly links that could now be outdated.

View example

Review launch links when a Spotify playlist is created

When a new Spotify playlist is created, retrieve recent Cutt ly URLs to help verify launch links before sharing.

View example

Review short links after a playlist is deleted

When a Spotify playlist is deleted, retrieve recent Cutt ly URLs and flag links that may need a manual destination review.

View example

Build a recent link inventory for new playlists

When a Spotify playlist is created or deleted, retrieve recent Cutt ly URLs and organize a concise inventory for catalog review.

View example

Review campaign links when a Spotify device is added

When a new Spotify device is added, retrieve recent Cutt ly URLs and send a focused review of links relevant to your listening setup or campaign.

View example

Create an event link brief after adding a Spotify device

After a new Spotify device is added, retrieve recent Cutt ly URLs and prepare a brief for the related event or listening session.

View example

Summarize shareable links after playlist updates

When a Spotify playlist changes, retrieve recent Cutt ly URLs and produce a short summary of links ready for sharing.

Supported Triggers and Actions

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

Spotify 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 Device Added

Triggers when a new device is added.

TriggerPolling

Spotify Playlist Item Change

Triggers when songs are added to or removed from a Spotify playlist.

TriggerPolling

New Playlist Created or Deleted

Triggers when a new playlist is created or deleted.

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.