Connect Fireflies to Anchor browser
When something happens in Fireflies, Notis takes the next step in Anchor browser. 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 Anchor browser
Check the webpage named in a completed meeting transcript
When Fireflies finishes a transcript, retrieve the rendered webpage referenced in the conversation so Notis can compare the live page with meeting decisions.
Capture a screenshot of a page discussed in a meeting
After a Fireflies transcription completes, use Anchor browser to capture a visual snapshot of a webpage named in the meeting.
Start a browser session for transcript follow-up
When a transcript completes, launch an isolated Anchor browser session so follow-up research starts with a clean workspace.
Upload a meeting brief for browser follow-up
Use a completed Fireflies transcript to prepare a brief file and upload it as an Anchor browser session resource for the next web task.
List resources available for a meeting follow-up session
After transcription completes, list files already attached to the relevant Anchor browser session and report what the team can use.
Index recordings for a completed meeting follow-up
When Fireflies completes a transcript, list recordings for the associated Anchor browser session so the team can revisit the browser work.
Check active browser sessions after a sensitive meeting
Use a completed Fireflies transcript to review the status of all active Anchor browser sessions when the call raises a security concern.
End a browser session requested in a meeting
When a completed Fireflies transcript explicitly requests closure, end the named Anchor browser session and report the result.
End all browser sessions after an explicit security decision
After a completed Fireflies transcript confirms an emergency security decision, end all active Anchor browser sessions for the authenticated user.
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Anchor browser. A trigger fires from one place; an action lands in another.
Fireflies triggers
Anchor browser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Profile
Tool to create a new browser profile from an active session. use after ending a session to persist cookies and cache.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Profile
Tool to delete a browser profile by id. use after confirming the profile exists.
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.
End All Sessions
Tool to end all active browser sessions. use after confirming a security concern when you need to immediately close every session for the authenticated user.
End Browser Session
Tool to end a specific browser session by id. use after confirming the session id you want to terminate.
Get Profile
Tool to fetch details for a specific browser profile by id. use after you know the profile id and need its settings and session information.
Get Webpage Content
Tool to retrieve rendered content of a webpage in html or markdown format. use when you need to fetch a page’s full content, optionally within an existing browser session.
List Agent Resources
Tool to list agent resources (files) for a given session. use after establishing a browser session to retrieve agent-uploaded files.
List All Sessions Status
Tool to list the status of all active browser sessions. use after authenticating when you need to retrieve an up-to-date overview of all sessions.
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 Anchor browser
Connect any two apps with Notis in the middle.
Fireflies and Anchor browser, 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 Anchor browser.