Connect Fireflies to Cutt ly

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

View example

Review recent short links after every transcribed meeting

After Fireflies finishes a transcription, Notis retrieves your latest Cutt ly links and highlights links that may support meeting follow-ups.

View example

Create a demo link recap from each completed transcript

When a Fireflies transcription completes, Notis fetches recent Cutt ly URLs and summarizes which ones could belong in the demo recap.

View example

Check partner meeting links after transcription

Notis compares a completed Fireflies partner meeting transcript with recently shortened Cutt ly URLs and calls out likely partner resources.

View example

Summarize investor call links after transcription

After an investor call is transcribed, Notis retrieves recent Cutt ly links and summarizes those connected to requests, metrics or next steps.

View example

Review customer call resources after every transcript

Notis reviews recent Cutt ly links against a completed Fireflies customer call and surfaces likely resources for support or follow-up.

View example

Build a launch planning link digest

When a launch planning transcript completes, Notis retrieves recent Cutt ly URLs and groups links that relate to launch decisions and tasks.

View example

Log links connected to team decisions

After a team meeting transcript completes, Notis retrieves recent Cutt ly URLs and records which links appear connected to decisions or owners.

View example

Create a content review link inventory

Notis uses a completed Fireflies content review transcript to identify related recent Cutt ly URLs and summarize their review status or purpose.

View example

Spot recurring link patterns in meeting follow-ups

After each completed Fireflies transcript, Notis retrieves recent Cutt ly URLs and flags recurring themes such as repeated resources or unresolved link follow-ups.

Supported Triggers and Actions

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

Fireflies 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

Transcription Complete Trigger

Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.

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.