Fireflies Search and AskFred Analysis

Overview

Keep deterministic transcript discovery separate from generative AskFred analysis. Search results identify candidate records; an AI answer is derived output and must retain meeting provenance.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The Fireflies principal, team, environment, and data classification for the work.
• Current Fireflies documentation, credentials only when needed, and an accountable approver.

Current Contract

transcripts supports keyword with scope TITLE, SENTENCES, or ALL, ISO-8601 fromDate/toDate, limit up to 50, skip pagination, mine, organizers, participants, and channel_id. title, organizer_email, and participant_email filters are deprecated. AskFred create/continue mutations consume AI credits.

Authentication

For authenticated operations, inject FIREFLIES_API_KEY from an approved secret manager and send it only as Authorization: Bearer REDACTED_KEY to https://api.fireflies.ai/graphql. Never print, commit, place in a URL, forward to a browser, or include the key in evidence. Webhook signing secrets are separate credentials and must not be reused as API keys.