Connect Mailchimp to Cutt ly

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

View example

Review short links after a Mailchimp campaign sends

When Mailchimp records a campaign event, retrieve the latest Cutt ly links and summarize which links may need attention before follow-up.

View example

Create a campaign link digest from Cutt ly

After a Mailchimp campaign event, gather recently shortened Cutt ly URLs into a concise digest for your marketing log.

View example

Check current short links after a subscriber profile update

When a Mailchimp profile changes, retrieve recent Cutt ly URLs and prepare link context for the next personalized follow-up.

View example

Triage link follow-up after Mailchimp profile changes

On each Mailchimp profile update, inspect the latest Cutt ly URLs and highlight what a founder should review next.

View example

Prepare a short link check for every new subscriber

When someone subscribes in Mailchimp, retrieve recent Cutt ly URLs and assemble a quick check for welcome journey links.

View example

Summarize link context for new Mailchimp subscribers

After a subscription event, gather recent Cutt ly URLs and produce a compact context summary for your next onboarding step.

View example

Review short links after an unsubscribe event

When a subscriber unsubscribes, retrieve recent Cutt ly URLs and prepare a focused review of links used in retention or preference updates.

View example

Build a preference link digest after unsubscribes

After Mailchimp records an unsubscribe, compile a concise digest of recent Cutt ly URLs for preference and lifecycle review.

Supported Triggers and Actions

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

Mailchimp 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

Campaign Trigger

Triggered when a campaign is sent or experiences an event in Mailchimp

TriggerInstant

Profile Update Trigger

Triggered when a subscriber's profile is updated in Mailchimp

TriggerInstant

Subscribe Trigger

Triggered when a subscriber subscribes to Mailchimp

TriggerInstant

Unsubscribe Trigger

Triggered when a subscriber unsubscribes from Mailchimp

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.