Connect Timelinesai to Cutt ly

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

View example

Check recent Cuttly links after a WhatsApp message

When a new TimelinesAI WhatsApp message arrives, retrieve recent Cuttly links and summarize their current details for quick follow-up.

View example

Prepare a WhatsApp link follow-up brief

After a new WhatsApp message, fetch recent Cuttly URLs and draft a short follow-up brief based on the returned link details and the message context.

View example

Triage WhatsApp requests involving links

When a WhatsApp message arrives, retrieve recent Cuttly URLs and classify whether the conversation needs a link response, verification, or human review.

View example

Add campaign link context to WhatsApp messages

For each new WhatsApp message, review recent Cuttly URLs and summarize any campaign or sharing context you provide in the automation prompt.

View example

Create a sales link recap from WhatsApp

When a new TimelinesAI WhatsApp message arrives, retrieve recent Cuttly links and produce a concise sales recap with open link related decisions.

View example

Review possible duplicate links after WhatsApp messages

After each new WhatsApp message, retrieve recent Cuttly URLs and flag likely duplicate or overlapping links for manual review.

View example

Create a link inventory snapshot on demand

Send a webhook to Notis to retrieve recent Cuttly URLs and return a structured inventory snapshot for the supplied business context.

View example

Generate a link sharing checklist from a webhook

When a webhook arrives, retrieve recent Cuttly URLs and produce a checklist for the sharing task described in the request.

View example

Review recent Cuttly links each morning

On a schedule, retrieve recent Cuttly URLs and deliver a morning review highlighting items that need your attention.

Supported Triggers and Actions

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

Timelinesai 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 WhatsApp Message Received

Polling trigger that monitors for new messages received in TimelinesAI WhatsApp chats.

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.