Connect Trello to Cutt ly

When something happens in Trello, 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 Trello to Cutt ly

View example

Review recent Cuttly links when a Trello card is created

When a Trello card is created, Notis retrieves your latest Cuttly URLs and summarizes links relevant to the card.

View example

Check Cuttly links when a Trello card changes

When a specific Trello card is updated, Notis checks recent Cuttly URLs and highlights link changes or follow-up needs.

View example

Review links when a Trello card is archived

When a card is archived, Notis retrieves recent Cuttly URLs and summarizes any links that may need retention or handoff.

View example

Turn Trello activity into a Cuttly link context digest

When Trello activity occurs, Notis retrieves recent Cuttly URLs and produces a focused digest for the affected work.

View example

Create a Cuttly baseline when a Trello board is created

When a Trello board is created, Notis retrieves recent Cuttly URLs and records a starting link baseline for the new workspace.

View example

Run a daily review of recent Cuttly links against Trello work

On a schedule, Notis retrieves recent Cuttly URLs and relates them to the Trello work context you specify.

View example

Prepare a weekly Cuttly link cleanup review

Each week, Notis retrieves recent Cuttly URLs and groups them into a cleanup and follow-up report for your Trello workflow.

View example

Generate a campaign link brief on demand

When your webhook receives a request, Notis retrieves recent Cuttly URLs and prepares a campaign brief for related Trello work.

View example

Flag possible duplicate links for new Trello cards

When a new Trello card is created, Notis retrieves recent Cuttly URLs and flags possible duplicates based on the card context.

Supported Triggers and Actions

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

Trello 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

Card Archived Trigger

Triggered when a card is archived in the specified board

TriggerInstant

New Activity Trigger

Triggered when there is activity in Trello.

TriggerInstant

New Board Trigger

Triggered when a board is created in the specified workspace

TriggerInstant

New Card Trigger

Triggered when a card is created in the specified board

TriggerInstant

Card Updated Trigger

Triggered when a specific card is updated

TriggerInstant

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.