Connect Coda to Cutt ly

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

View example

Review Cuttly links when a Coda document is created

When a new Coda document appears, Notis retrieves your latest Cuttly links and reports which links may belong in the new project context.

View example

Add Cuttly link context when a Coda page is added

When a new Coda page is added, Notis checks recent Cuttly URLs and highlights links that could support the page topic.

View example

Check link drift after a Coda page update

When a specific Coda page changes, Notis reviews recent Cuttly links and flags possible outdated or inconsistent references for follow-up.

View example

Review Cuttly links after a Coda document is deleted

When a Coda document is deleted, Notis retrieves recent Cuttly links and reports which ones may need retirement or ownership review.

View example

Run an on-demand Coda and Cuttly link audit

Send a webhook when a Coda review is needed, and Notis retrieves recent Cuttly URLs for a focused audit using the context in the request.

View example

Review recent Cuttly links for weekly Coda hygiene

On a schedule, Notis retrieves recent Cuttly URLs and prepares a weekly review of links referenced by your Coda work, using criteria you provide.

View example

Reconcile campaign links for monthly Coda planning

Before monthly planning, Notis retrieves recent Cuttly links and groups likely campaign links for review against the Coda planning context you provide.

View example

Send a daily Cuttly link pulse for Coda standups

Each morning, Notis retrieves recent Cuttly URLs and summarizes the links relevant to the Coda work items and standup context you provide.

Supported Triggers and Actions

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

Coda 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

Coda Document Deleted Trigger

Triggers when a Coda document is deleted.

TriggerPolling

New Coda Document Trigger

Triggers when a new Coda document is created.

TriggerPolling

New Coda Page Trigger

Triggers when a new page is added to a Coda document.

TriggerPolling

Specific Coda Page Updated Trigger

Triggers when a specific page within a Coda document is updated.

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.