Connect Outlook to Cutt ly

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

View example

Review recent short links when a new Outlook message arrives

When a new Outlook message arrives, Notis reviews your latest Cuttly links and highlights links relevant to the conversation.

View example

Log recent Cuttly links after sending an Outlook message

After you send an Outlook message, Notis checks recent Cuttly URLs and reports which links may have been included or need tracking.

View example

Prepare links for a new Outlook calendar event

When a new calendar event is created, Notis reviews recent Cuttly URLs and prepares a link brief for the meeting.

View example

Refresh link context when an Outlook event changes

When an Outlook calendar event is created, updated, or deleted, Notis reviews recent Cuttly URLs and reports what link context may need attention.

View example

Build a link context note for each new Outlook contact

When a new Outlook contact is added, Notis reviews recent Cuttly URLs and summarizes links that may support the relationship.

View example

Run a daily review of recent Cuttly links

On a schedule, Notis reviews your latest Cuttly URLs and sends a daily brief of links needing follow up or clearer organization.

View example

Check recent Cuttly links when a campaign webhook fires

When your system sends a webhook, Notis reviews recent Cuttly URLs and returns a campaign focused link check.

View example

Prioritize link follow ups from new Outlook messages

For each new Outlook message, Notis reviews recent Cuttly URLs and ranks any link related follow ups by urgency.

View example

Check recent Cuttly links after outbound email

After a sent Outlook message, Notis reviews recent Cuttly URLs and flags possible missing, duplicate, or unclear link usage.

Supported Triggers and Actions

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

Outlook 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 Contact Added

Triggered when a new contact is added in the Outlook contacts.

TriggerInstant

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

TriggerInstant

New Calendar Event

Triggered when a new calendar event is created in the Outlook calendar.

TriggerInstant

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

TriggerInstant

New Sent Message

Triggered when a new message is sent from the Outlook mailbox.

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.