Skip to main content
A read-only API key integration that syncs Fireflies meeting transcripts and AI summaries into Rippit on a schedule. For what applies to every integration, see how data integrations work. For the security model, see Data integration security. This page covers the data integration, which imports your Fireflies meetings into Rippit. To let the Rippit agent search Fireflies live during a chat instead, see the Fireflies MCP server.

Connection summary

Before you connect

Rippit asks for two values:
  • API key. Create it in Fireflies under Settings → Developer Settings. A team admin’s key returns meetings for the whole Fireflies team. A key from any other user returns only what that user can see in Fireflies.
  • Workspace name. A label for the connection in Rippit, such as your team or company name. It is not sent to Fireflies.

Data handling

What a meeting becomes in Rippit

Each Fireflies meeting becomes one conversation in Rippit. Consecutive sentences from one speaker join the same turn until there is a pause of more than 3 seconds or the turn reaches 1,000 characters. Each turn carries the speaker name Fireflies identified. A sentence with no speaker name shows no name in Rippit, and consecutive unnamed sentences join one turn. The organizer’s display name comes from the matching Fireflies user or attendee record. When neither has a name, the summary comment and agent list use the organizer’s email, and the Organizer name field is empty. Links from Rippit to a meeting open its Fireflies URL.

API endpoints

Every call is a POST to https://api.fireflies.ai/graphql. The query in the request body determines what is read. The transcripts query requests these fields: There is no separate per-meeting fetch. The list query returns each meeting’s summary and full transcript inline, so one paged query both discovers meetings and reads their content. No other Fireflies object is listed or swept. Organizer and attendees come from the transcript record itself.

Sync behavior

Rate limiting

  • Every request, retries included, starts at least 2 seconds after the previous one, so a sync sends at most 30 requests per minute, within the Free plan’s per-minute limit.
  • Fireflies caps API requests by plan. Free allows 500 per day and Pro 5,000 per day. Business and Enterprise have no daily cap. A backfill or a busy day can exhaust a daily cap. When it does, the sync fails until Fireflies resets the quota, and the connection stays valid.
  • Each page of up to 50 meetings is one request. Each sync also spends one request on the credential check.