Fireflies Error Taxonomy and Recovery

Overview

Diagnose Fireflies transport, GraphQL, permission, plan, processing, and operation-limit failures without unsafe retries or data probing.

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

Separate HTTP failures from top-level GraphQL errors and domain state. Normalize auth_failed, object_not_found, invalid_args or invalid_arguments, require_elevated_privilege, require_ai_credits, too_many_requests, unsupported_platform, and processing-state nulls.

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.