Fireflies integration

What Management OS does with your Fireflies data.

Operator-grade transparency. The API permissions we use map to specific Management OS features you can see and measure. Nothing pulled, nothing stored, nothing inferred beyond what this page documents.

1. What we read

Management OS reads meeting data from your Fireflies workspace via the Fireflies GraphQL API — specifically: meeting metadata (title, date, duration, host, attendees), full transcripts, AI-generated summaries, and action items. We do not access raw audio files, account billing data, team admin settings, or any Fireflies data not explicitly listed below.

Why: Meeting transcripts are the highest-signal source on a revenue team — what the champion actually said, what the buyer actually objected to, what the rep actually committed. Management OS reads those transcripts so Account Plans, Coaching Briefs, and the Weekly Brief reflect the real conversation rather than CRM stage labels.

2. What we write

We do not write to your Fireflies workspace. Management OS is a read-only consumer of your Fireflies data. We do not create, modify, or delete any Fireflies records — no meetings, no summaries, no transcripts, no tags, no comments, no shares.

All Management OS outputs (Account Plans, Coaching Briefs, Meeting Prep dossiers, Weekly Briefs) are generated and stored in Management OS's own database and surfaced through the Management OS application — not pushed back into your Fireflies workspace.

3. The API permissions we request

Fireflies uses a single per-user API key rather than granular OAuth scopes. The key inherits the permissions of the user who generated it. When you connect, Management OS uses the key only for the read operations below; nothing else. We never call mutation endpoints.

Read-only operations we call

These are the only GraphQL queries Management OS runs against your Fireflies API. We do not call any mutation, upload, or admin endpoints.

user

Read the connected user's Fireflies identity (user_id, email, name) so Management OS can map the connection to the right workspace member and so attendee/host matching works correctly.

transcripts (read)

Read full meeting transcripts via the `transcript` and `transcripts` GraphQL queries — the source material that feeds Meeting Prep dossiers, Coaching Briefs, and Account Plan updates with real quotes instead of paraphrases.

meetings + metadata (read)

Read meeting metadata (title, date, duration, host, attendees, calendar mapping) so each transcript can be matched to the right account, deal, and rep before it ever feeds a brief.

AI summaries + action items (read)

Read Fireflies AI summaries, action items, and key moments so the Weekly Brief can surface what was committed in the room and route post-call follow-up gaps to the right rep's coaching priorities.

The key you generate inherits your Fireflies user's meeting access. If you want only your own recordings to be readable, generate the key under your individual user. If you want team-wide coverage, an admin can generate the key under a user that has team-meeting access in Fireflies.

4. Where your Fireflies data lives

Application database: Supabase Postgres (Management OS's production database, US East). Encrypted at rest (AES-256), encrypted in transit (TLS 1.3). Workspace-scoped row-level security (RLS) means one customer's data is never visible to another.

API key: Stored in the same Supabase database under workspace-scoped RLS. The key is encrypted at rest and never returned to client browsers. Only the Management OS server-side runtime has access via service-role credentials.

Inference layer: Anthropic API (Claude models). Transcript and summary data required for a specific brief or dossier generation is passed to Anthropic; outputs are returned to Management OS and stored in our database. Anthropic does not train on customer data per their API terms.

Retention: We retain Fireflies-sourced data while your subscription is active. On disconnect we delete the API key immediately. On subscription cancellation, customer data is retained for 30 days for restoration, then permanently deleted. Data subject deletion requests are honored within 30 days per our Privacy Policy.

5. How to install Management OS for Fireflies

  1. Sign in to Fireflies at app.fireflies.ai
  2. Open Settings → Developer Settings (or API, depending on Fireflies plan)
  3. Click Generate API Key and copy the key — Fireflies shows it once
  4. In Management OS, open Settings → Integrations and find Fireflies in the integration directory
  5. Click Connect Fireflies, paste the API key, and submit. Management OS validates the key with a live call before saving
  6. On success, the initial meeting sync starts immediately and typically completes within 2-5 minutes for recent meetings; full-history backfill continues in the background

If you administer Fireflies on behalf of a team: The API key inherits the permissions of the user who generated it. For team-wide coverage, generate the key under a user that has access to team meetings (typically a workspace admin), or have each rep connect their own key.

6. How to use Management OS once connected

Fireflies transcripts feed three primary Management OS surfaces:

  • Meeting Prep dossiers — before your next call with an account, Management OS pulls every prior Fireflies transcript on that account, surfaces the open commitments, the unresolved objections, the champion language, and the next-step laddering — so you walk into the room with peer-operator context, not a CRM summary
  • Coaching Briefs — managers see GROW-structured coaching prep based on what actually happened in the rep's recent calls. Discovery depth, objection handling, multi-thread coverage, next-step clarity — all scored from real transcripts against the 17 sales competencies
  • Account Plan updates — every transcript on an account auto-updates the Strategic Account Plan across the 8 canonical dimensions (relationship, Porter, buying committee, value, risks, next plays). The plan reflects the latest conversation, not last quarter's snapshot

The Weekly Intelligence Brief synthesizes across all three with the three pillars — Develop Your Business, Develop Your Team, Develop Yourself. Ask Anything (AMA) lets you query transcripts in plain English: "What did the Acme CFO say about budget timing on the last call?", "Which deals have no champion activity in the last 14 days of recorded meetings?"

7. How to disconnect from Management OS

  1. Open Management OS → Settings → Integrations
  2. Find Fireflies in the connected integrations list
  3. Click Disconnect → confirm

On disconnect we immediately delete the stored API key and stop reading any new meeting data. Previously synthesized briefs and dossiers remain in your Management OS workspace as historical records — they are not deleted automatically because they may contain decisions and context the leader still references.

To remove all historical briefs and data after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.

8. How to revoke from Fireflies's side

  1. Sign in to Fireflies at app.fireflies.ai
  2. Open Settings → Developer Settings (or API)
  3. Find the API key issued to Management OS in the keys list
  4. Click Revoke (or Regenerate, which invalidates the prior key)

Revoking from Fireflies's side invalidates the key immediately. Our next GraphQL call returns an authentication error and we surface a re-connection prompt in Management OS Settings.

9. Security disclosures + contact

Security incident reporting: security@mgmt-os.ai
Privacy / data subject requests: privacy@mgmt-os.ai
Integration support: support@mgmt-os.ai

For general questions about Management OS, see our Support page or Manifesto.

Last updated: 2026-11-01. We update this page within 7 days of any change to scopes, data flows, or retention.