> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getomni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Fireflies

> Connect Fireflies.ai to Omni for unified search across meeting transcripts, summaries, and action items

The Fireflies connector enables Omni to index and search content from your Fireflies.ai account, including meeting transcripts, summaries, and action items.

## 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

1. You provide a Fireflies API key with read access
2. The connector fetches transcripts via the Fireflies GraphQL API
3. Transcripts are formatted with metadata, summaries, and full conversation text
4. Incremental sync fetches only meetings added since the last sync

<Note>
  The connector uses read-only access. Omni cannot modify any content in your Fireflies account.
</Note>

## 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

1. Log in to [Fireflies.ai](https://app.fireflies.ai)
2. Go to **Settings** → **Developer Settings**
3. Generate a new **API key**
4. Copy the API key

<Warning>
  Keep your API key secure. Anyone with access to this key can read meeting transcripts from your Fireflies account.
</Warning>

### Step 2: Connect in Omni

1. Navigate to **Settings** → **Integrations** in Omni
2. Find **Fireflies** and click **Connect**
3. Enter your Fireflies API key
4. Click **Connect**
5. Click **Sync Now** to start the initial sync

<Check>
  Your Fireflies connector is now configured. Initial indexing may take a while depending on the number of transcripts in your account.
</Check>

## Managing the Integration

### Viewing Sync Status

Navigate to **Settings** → **Integrations** to view the sync status for each source directly on the list, including last sync time, number of indexed items, and any errors. Click **Configure** on a source for more details.

### 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) |

After the initial full sync, the connector automatically performs incremental syncs to capture new transcripts.

### Removing the Integration

1. Navigate to **Settings** → **Integrations**
2. Click **Configure** against the Fireflies source
3. Click **Delete Permanently**

## Troubleshooting

<AccordionGroup>
  <Accordion title="Transcripts not appearing in search">
    Common causes:

    * Sync has not completed yet
    * API key does not have access to the transcripts

    **Solution**: Verify your API key permissions and trigger a manual sync.
  </Accordion>

  <Accordion title="API key validation failed">
    The API key may be expired or revoked.

    **Solution**:

    1. Go to your Fireflies developer settings
    2. Generate a new API key
    3. Update the key in Omni via **Settings** → **Integrations** → **Fireflies**
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## 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

<CardGroup cols={3}>
  <Card title="Search Your Data" icon="magnifying-glass" href="/user-guide/search">
    Learn how to search across meeting transcripts
  </Card>

  <Card title="AI Assistant" icon="robot" href="/user-guide/ai-assistant">
    Ask questions about your meetings
  </Card>

  <Card title="Add More Connectors" icon="plug" href="/connectors/overview">
    Connect additional data sources
  </Card>
</CardGroup>