#4738·cognee

Hackathon [Feature]: Add Fireflies data-source connector

Author: NMZivkovicCreated Aug 28, 2026Updated Sep 12, 2026
Labelsenhancementgood first issueINTEGRATIONShackathon

Problem Statement

cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project.

Fireflies is on the roadmap and has no connector.

Proposed Solution

Add a fireflies connector under packages/connector/fireflies/ in cognee-community, following the shape of the five existing connectors.

  • Auth: API key, GraphQL
  • Ingest: transcripts, summaries, action items, and speakers
  • Incremental sync: transcript date cursor
  • Forget-on-delete: deleting upstream must remove the record from the graph on the next sync

Watch out for

Speaker attribution is the differentiator — carry speakers into the graph as entities, not flat text.

Package layout to follow

packages/connector/fireflies/
├── README.md
├── cognee_community_connector_fireflies/
│   ├── __init__.py
│   └── fireflies.py
├── examples/
├── tests/
└── pyproject.toml

Read packages/connector/notion/ first — it is the closest working reference.

Acceptance Criteria

  • A user connects via API key, GraphQL and selects what to ingest
  • Selected content is ingested and searchable in cognee
  • Incremental sync picks up only what changed since the last run
  • Deleting the source upstream removes it from the graph on the next sync
  • README with setup steps and a runnable example under examples/
  • Tests covering the ingest path and the incremental cursor

Context

Part of the cognee hackathon connector push. Difficulty: Beginner friendly (E) — auth is an API key or token; no OAuth dance, no account gatekeeping