Zentrik

Zentrik + Fireflies

Bring selected Fireflies transcripts into Discovery as reviewed, traceable signal with transcript-backed evidence.

Admins save one workspace credential in Settings → Integrations.

Fireflies connects with a workspace API key saved by an admin. Zentrik uses that key server-side to search Fireflies, preview transcript text, and import only the transcripts you select.

Use this integration when meeting transcripts already live in Fireflies and your product team needs selected conversations to become durable Discovery evidence. Imported transcripts become Discovery signals first. Zentrik then processes them through the normal signal-to-insight workflow, so ideas and roadmap decisions stay traceable to the original call.

Fireflies import dialog showing neutral example transcripts before import.

Review Fireflies transcripts before import: filter the list, preview source text, and send only selected ready transcripts into Discovery.

Before you connect

Pick the Fireflies identity intentionally. The API key decides which transcripts Zentrik can see, so use an account or shared admin identity that has access to the conversations your team is allowed to import.

Before saving the key:

  1. Confirm the transcript is visible in Fireflies to the account that will own the API key.
  2. Confirm your team is allowed to bring those conversations into Zentrik for product discovery.
  3. Decide the first import window and filters: date range, participant email, organizer email, and keywords that identify calls with product signal.

Do not use a personal key that only sees a narrow or accidental slice of meetings unless that is the intended boundary. If the key cannot see a transcript in Fireflies, Zentrik cannot import it.

Connect Fireflies

Create the integration in Settings -> Integrations -> Fireflies and paste a Fireflies API key that has access to the transcripts your product team should import.

API key

  1. Log in to Fireflies as the account that should own the Zentrik connection.
  2. Open Integrations, choose Fireflies API, and copy the API key.
  3. In Zentrik, open Settings -> Integrations -> Fireflies.
  4. Paste the API key and save.
  5. Use Test connection or run a small Discovery transcript scan to confirm Zentrik can reach Fireflies.

Secrets are stored server-side; Zentrik does not show them again after save. Fireflies treats API keys like bearer tokens, so rotate the key in Fireflies and update Zentrik if the key may have been exposed.

Fireflies reference: Authorization and how to get your API key.

How to use it

Open Discovery, click New, choose Bring in data, and select Fireflies. Pick a date range, narrow the results when needed, then review the matching transcripts before importing.

Import transcripts

  1. Choose the date range that contains the conversations you want to evaluate.
  2. Use Keyword to search transcript text or titles. Set Search scope to All, Title, or Transcript depending on how specific the phrase is.
  3. Use Organizer emails when the right calls were run by a known teammate.
  4. Use Participant emails when you know who should appear on the call.
  5. Click Find transcripts.
  6. Review the results. Already-imported transcripts are marked, and live or still-processing transcripts cannot be imported yet.
  7. Preview transcript text when you need to confirm the call contains product signal.
  8. Select only the ready transcripts that should become Discovery signals.
  9. Click Import selected.

After import, Zentrik stores the transcript snapshot, source links, participant and organizer metadata, Fireflies privacy metadata, summary fields, and speaker-attributed transcript text. The signal then processes in the background so insights can be proposed and traced back to the call.

Use Fireflies imports for calls where the transcript itself is the evidence you want PMs and leaders to trace back to: product gaps, repeated workflow pain, support escalations, and moments where a participant explains why a problem matters.

Progress state while Zentrik processes an imported meeting transcript into Discovery evidence.

After import, Fireflies transcripts follow the same signal -> insight path as other transcript sources.

For workspace admins

  • One workspace key keeps imports centralized for v1.
  • The connected Fireflies key controls what Zentrik can list, preview, and import.
  • The key remains server-side. Users importing from Discovery do not see the secret.
  • Fireflies transcript visibility, privacy, sharing, and retention remain the source of truth. If a transcript is not available to the connected key, Zentrik cannot import it.
  • Rotate the key in Fireflies and update Zentrik whenever your security policy requires it.
  • For sensitive or restricted conversations, confirm consent and internal data policy before importing transcripts into Discovery.

Troubleshooting

Check credentials and permissions on both sides first. If you have verified everything and it still fails, contact us with your workspace name and what you tried.

Credentials not working

Generate a new API key in Fireflies, paste it into Settings -> Integrations -> Fireflies in Zentrik, and save again. Watch for extra spaces when copying, and make sure the key comes from the Fireflies account that should own the workspace connection.

Transcript missing from the review list

Confirm the transcript is visible in Fireflies to the same account that owns the API key. Then widen the date range, remove keyword filters, or search by organizer or participant email. If it still does not appear, the connected key likely does not have access to that meeting.

Transcript cannot be imported

Live or still-processing meetings are not importable until Fireflies has produced the transcript. If Zentrik says the transcript is unavailable to the API key, ask the Fireflies admin to share the meeting with the connected account or connect a key that has access. Fireflies can report a transcript as not found when the key does not have access to it.

Still failing

Contact us with your workspace name, the Fireflies transcript title or date, and the filter values you tried. Do not send API keys or full transcript text in the support request.