Overview
What Gets Indexed
| Source | Content |
|---|---|
| Transcripts | Full meeting transcripts with speaker names and timestamps |
| Summaries | AI-generated overviews, outlines, and bullet points |
| Action Items | Tasks and follow-ups extracted from meetings |
| Metadata | Meeting title, date, duration, participants, and keywords |
How It Works
- You provide a Fireflies API key with read access
- The connector fetches transcripts via the Fireflies GraphQL API
- Transcripts are formatted with metadata, summaries, and full conversation text
- Incremental sync fetches only meetings added since the last sync
The connector uses read-only access. Omni cannot modify any content in your Fireflies account.
Prerequisites
Before setting up the Fireflies connector, ensure you have:- Fireflies.ai account with API access
- Omni deployment with the Fireflies connector service running
Setup
Step 1: Generate a Fireflies API Key
- Log in to Fireflies.ai
- Go to Settings → Developer Settings
- Generate a new API key
- Copy the API key
Step 2: Connect in Omni
- Navigate to Settings → Integrations in Omni
- Find Fireflies and click Connect
- Enter your Fireflies API key
- Click Connect
- Click Sync Now to start the initial sync
Your Fireflies connector is now configured. Initial indexing may take a while depending on the number of transcripts in your account.
Managing the Integration
Viewing Sync Status
Navigate to Settings → Integrations to view:- Last sync time
- Number of indexed transcripts
- Any sync errors
Sync Modes
The Fireflies connector supports two sync modes:| Mode | Description |
|---|---|
| Full | Syncs all available transcripts (used for initial sync) |
| Incremental | Syncs only transcripts added since the last sync (used for updates) |
Removing the Integration
- Navigate to Settings → Integrations → Fireflies
- Toggle the Enabled switch off.
Troubleshooting
Transcripts not appearing in search
Transcripts not appearing in search
Common causes:
- Sync has not completed yet
- API key does not have access to the transcripts
API key validation failed
API key validation failed
The API key may be expired or revoked.Solution:
- Go to your Fireflies developer settings
- Generate a new API key
- Update the key in Omni via Settings → Integrations → Fireflies
Rate limiting errors
Rate limiting errors
Fireflies has API rate limits. If you hit a rate limit, the sync will fail.Solution: Wait a few minutes and trigger a new sync. For accounts with many transcripts, the initial sync may need multiple attempts.
Security Considerations
- Read-only access: The connector only reads transcript data
- Token security: API keys should be treated like passwords
- Encrypted storage: Credentials are encrypted at rest in Omni
What’s Next
Search Your Data
Learn how to search across meeting transcripts
AI Assistant
Ask questions about your meetings
Add More Connectors
Connect additional data sources