Connect Fireflies to Browserbase tool
When something happens in Fireflies, Notis takes the next step in Browserbase tool. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Fireflies to Browserbase tool
Open a Browserbase session for every completed meeting transcript
Start an isolated browser session whenever Fireflies finishes a transcription so follow-up web research can begin immediately.
Review network activity from meeting follow-up browsing
When a Fireflies transcript completes, retrieve Browserbase session logs so technical follow-up can be checked for requests and failures.
Download browser artifacts linked to a completed call
Use a finished Fireflies transcription to request Browserbase session artifacts for review, sharing, or archival.
Check browser session status after every transcript
When Fireflies finishes a transcription, retrieve the related Browserbase session details and report whether follow-up work is running or complete.
Create a live debug link for urgent meeting follow-up
After a Fireflies transcription completes, retrieve live Browserbase debug URLs for a running session that needs inspection.
Close browser sessions after meeting work is complete
Use a completed Fireflies transcript as the signal to request completion of a related Browserbase session and avoid unnecessary runtime charges.
Check browser context metadata for meeting research
When a Fireflies transcript is ready, retrieve Browserbase context details to confirm the right isolated workspace is available.
Refresh browser context credentials after a transcript
After Fireflies completes a transcription, update a known Browserbase context to obtain fresh upload URL and encryption details for follow-up work.
Start browser research from a transcript webhook
Send a webhook when a transcript needs research and let Browserbase create an isolated session for the investigation.
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Browserbase tool. A trigger fires from one place; an action lands in another.
Fireflies triggers
Browserbase tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new browser context
Tool to create a new browser context. use when you need to obtain upload credentials for a custom user-data-directory in a project.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve a browser context
Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.
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.
Update Browser Context
Tool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.
Create Browser Session
Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
Retrieve a browser session
Tool to retrieve details of a specific browser session. use when you have a session id and need its metadata (status, urls, timestamps).
Retrieve Session Debug URLs
Tool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.
Download Session Artifacts
Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
Retrieve Session Logs
Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Fireflies and Browserbase tool
Connect any two apps with Notis in the middle.
Fireflies and Browserbase tool, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Browserbase tool.