Connect Fireflies to Bookingmood

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

View example

Update Bookingmood details from meeting changes

Extract confirmed guest or reservation changes from a completed Fireflies transcript and update matching Bookingmood booking details.

View example

Capture accessibility requests from call transcripts

Find accessibility or accommodation requests in Fireflies transcripts and add them to the matching Bookingmood booking details.

View example

Sync agreed arrival instructions

Extract confirmed arrival or check-in instructions from Fireflies transcripts and update matching Bookingmood details.

View example

Update guest contact preferences from calls

Extract confirmed communication preferences from Fireflies transcripts and update the relevant Bookingmood booking details.

View example

Remove details for confirmed cancellations

Detect confirmed cancellation decisions in completed Fireflies transcripts and delete matching Bookingmood booking details after review rules are met.

View example

Create a Bookingmood widget after a launch decision

When a Fireflies transcript confirms a new rental launch, create the requested Bookingmood booking widget.

View example

Review Bookingmood widgets after an operations meeting

After a Fireflies transcript, list Bookingmood booking widgets so Notis can report the current configurations relevant to the meeting.

View example

Identify the Bookingmood organization for a new property

Use a completed Fireflies transcript to identify the right Bookingmood organization before property setup work continues.

View example

Update an urgent booking detail from a webhook

When another system sends a Notis webhook with a confirmed booking change, update the matching Bookingmood booking details.

Supported Triggers and Actions

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

Fireflies triggers

Bookingmood actions

Recurring trigger

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

TriggerScheduled

Create Booking Widget

Tool to create a new booking widget. use after preparing widget parameters.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Booking Details

Tool to delete booking details matching given filters. use after confirming which booking detail records to remove.

ActionInstant

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

List Organizations

Tool to list organizations. use when you need to retrieve all organizations accessible by the current api key.

ActionInstant

List Booking Widgets

Tool to list booking widgets. use when you need to fetch available widget configurations.

ActionInstant

Deprecated: Search availability

Deprecated: replaced by search availability.py

ActionInstant

Update Booking Details

Tool to update existing booking detail records. use when modifying guest-filled form fields for bookings matching specific filters.

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.