Connect Fireflies to ClickHouse

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

View example

Query ClickHouse with every completed Fireflies transcript

Turn each completed meeting transcript into a focused ClickHouse query for metrics, trends, or follow-up analysis.

View example

Inspect the right ClickHouse table for meeting follow-up

Use each completed transcript to identify the ClickHouse table schema needed for a reliable follow-up query.

View example

Review database structure after a strategic meeting

After each completed transcript, get a ClickHouse database overview related to the decisions and questions raised.

View example

Discover ClickHouse databases mentioned in meetings

Use completed Fireflies transcripts to list ClickHouse databases that may contain data for a new initiative.

View example

Find ClickHouse tables for meeting action items

List ClickHouse tables related to action items and questions extracted from a completed Fireflies transcript.

View example

Run a daily ClickHouse query from recent meeting questions

On a schedule, query ClickHouse using the latest meeting questions you provide to Notis and receive a focused report.

View example

Create a weekly ClickHouse schema brief for meeting planning

Generate a scheduled overview of database structure to prepare for recurring planning and review meetings.

View example

Review ClickHouse table growth each week

Run a scheduled table inventory to spot large or fast changing areas before they become planning surprises.

View example

Query ClickHouse when a meeting review request arrives

Trigger a focused ClickHouse query from an HTTP request containing a meeting review question or decision context.

Supported Triggers and Actions

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

Fireflies triggers

ClickHouse actions

Recurring trigger

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

TriggerScheduled

Execute ClickHouse Query

Execute a sql query in clickhouse and return the results. this is the primary action for querying data from clickhouse databases.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Database Schema

Get comprehensive schema overview of an entire database including all tables and optionally their column definitions. essential for ai agents to understand the complete database structure in a single call.

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

Get Table Schema

Get detailed schema information for a specific table including column definitions, types, keys, and optionally sample data. this is essential for ai agents to understand table structure before constructing queries.

ActionInstant

List ClickHouse Databases

List all databases in the clickhouse instance. useful for discovering available databases before querying tables.

ActionInstant

List ClickHouse Tables

List tables in clickhouse databases. returns information about tables including their engine, size, and row count.

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.