Skip to main content
Configview reads your Fireflies.ai team through the Fireflies GraphQL API (https://api.fireflies.ai/graphql), using an API key copied from the Fireflies web app. Configview sends only read queries. It never creates, changes, shares or deletes anything in Fireflies. You will end up with 1 required secret (FIREFLIES_API_KEY) in Configview when setup is complete.
Scope of this integration today. Configview reads the team roster (name, work email, admin flag, meetings recorded, minutes consumed, most recent meeting, connected integrations, calendar sync state), user groups and their members, meeting metadata for the last 90 days (owner, date, duration, privacy setting, calendar type, meeting platform host, and counts of participants, attendees and outside attendees), and, on Enterprise plans, the audit log for the last 30 days. It never reads titles, transcripts, sentences, summaries, action items, keywords, speakers, audio or video files or their URLs, attendee names or email addresses (only counts are stored), audit message text or metadata.

Read this first: an API key has its owner’s access

A Fireflies API key cannot be scoped or made read-only. It sees what the user who copied it can see.
  • Use the key of a team admin on a Business or Enterprise plan. Only then can Configview expect to see the whole team roster and other members’ meetings (the docs do not say this explicitly; see the first-run checks below).
  • On Free or Pro, or with a non-admin key, the roster and meeting list may cover only that one person. Configview reports what the API returns.
  • The audit log needs an Enterprise plan and a team admin key. On other plans that collector is skipped, not failed.
  • Store the key only in Configview and rotate it (Fireflies lets you regenerate it) if its owner leaves.

What the Fireflies API does not tell Configview

There is no query for API keys, webhooks, per-user seats bought versus assigned, 2FA or SSO status, pending invitations or per-month usage. Webhooks are set up in the web app only. Configview cannot answer those questions.

What you need

  • A Fireflies.ai team (Business or Enterprise recommended)
  • A team admin who can open Integrations > Fireflies API

Step 1: Open the Fireflies.ai page in Configview

https://{companyname}.configview.com/admin/integrations/fireflies

Step 2: Copy the key

  1. Signed in to Fireflies as the admin, open Integrations, then Fireflies API (app.fireflies.ai/integrations/custom/fireflies)
  2. Copy the API key
  3. In Configview paste it into FIREFLIES_API_KEY under Credentials and click the save icon

Step 3: Connect and verify

  1. Click Connect. Configview creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secret and runs one small query for the key’s owner.
If a check fails: 401 or an auth_failed error means the key was regenerated or mistyped. 429 means the per-minute limit was hit; retry in a minute.

Data Tables

Each table has a run_at column and keeps only the newest run.

Rate limits

Fireflies limits requests per API key: 30 per minute and 500 per day on Free, 60 per minute and 5,000 per day on Pro, and 60 per paid seat per minute (pooled, up to 1,200 on Business and 2,400 on Enterprise) with no daily cap on Business and Enterprise. Configview paces at 25 per minute, reads 50 meetings per request (the maximum) and retries a 429 after the Retry-After header. A large meeting history on a Free or Pro plan can take several runs of the daily allowance.

Known gaps and things to check on the first run

These come from the published API documentation; no live tenant has been tested yet.
  • Whole team visibility. The docs do not state that an admin key lists every member’s meetings. If fireflies_transcripts only holds the key owner’s meetings, the owner and external-attendee questions cover just that person.
  • Field types. recent_meeting is assumed to be a timestamp or epoch value, duration is assumed to be minutes, and integrations, participants and fireflies_users are assumed to be lists of strings. A wrong assumption shows as NULL columns.
  • External attendees. Counted as attendee emails whose domain differs from the meeting owner’s domain. A company with several domains over-counts.
  • Privacy values. The privacy column holds the Fireflies setting (link, owner, participants, teammates, teammatesandparticipants). Only link is treated as open to anyone with the URL.
  • Audit log. Enterprise only. The failed sign-in query assumes a status other than success marks a failure.

Things worth knowing

Link-shared meetings. A meeting set to link can be opened by anyone with the URL. If it also had outside attendees (customers, candidates), review it first. Leavers. A member with no recent meeting still holds a seat and calendar access. Remove them in Fireflies when they leave.