Connect Linear to Fireflies

When something happens in Linear, Notis takes the next step in Fireflies. 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 Linear to Fireflies

View example

Find meeting context for new Linear issues

When a Linear issue is created, find relevant Fireflies transcripts so the issue can be reviewed with its meeting context close at hand.

View example

Review meeting transcripts when issues change

When a Linear issue changes, retrieve a relevant Fireflies transcript for a focused review of decisions or next steps that may affect the update.

View example

Check meeting outputs for new issue comments

When a Linear comment arrives, look for Fireflies AI app outputs tied to a relevant meeting or transcript to surface supporting decisions and follow-ups.

View example

Cross-check project updates against meeting transcripts

When a Linear project update is posted, search Fireflies transcripts for conversations that may support or clarify its status and next steps.

Supported Triggers and Actions

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

Linear triggers

Fireflies actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add to Live Meeting

The addtolive action allows you to add the fireflies.ai bot to an ongoing meeting. note: this action requires a paid fireflies plan to add bots to meetings.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Transcript by ID

The deletetranscriptbyid action is designed to delete a specific transcript by its id.

ActionInstant

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Fetch AI App Outputs

Fetch outputs for a specific ai app or meeting/transcript.

ActionInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Get Bite by ID

The getbite action is designed to fetch details associated with a specific bite id.

ActionInstant

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

TriggerInstant

Get Transcripts

The getbites action is designed to fetch a list of bites against input arguments.

ActionInstant

Private Team Comment Created

Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).

TriggerPolling

Get Transcript by ID

The gettranscriptbyid action is designed to fetch details associated with a specific transcript id. note: this action requires a paid fireflies plan to access transcript details.

ActionInstant

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

Get Transcripts

The gettranscripts action is designed to fetch a list of transcripts against input arguments.

ActionInstant

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

TriggerPolling

Get User by ID

The getuser action is designed to fetch details associated with a specific user id.

ActionInstant

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.