Fireflies.ai
DOCS & KNOWLEDGE · FILES & DOCS
Meeting transcripts, AI summaries, action items, and analytics in that workspace.
Connecting Fireflies.ai in practice
The quota is counted per day rather than per minute on the smaller plans — 50 requests a day on Free and 500 on Pro, against 60 a minute on Business and Enterprise — so a single backfill can consume a Free account’s entire day. The credential is a personal bearer key copied from one user’s Integrations page, with no scopes to narrow.
Rate limits
- 50 requests per day on Free, 500 per day on Pro, 60 requests per minute on Business and Enterprise.
- Add to Live API: 3 requests per 20 minutes.
- Share Meeting API: 60 requests per hour, up to 50 email addresses per request.
- Uploads: audio up to 200 MB for everyone; video 100 MB on Free and up to 1.5 GB on Pro, Business and Enterprise.
Worth knowing
- A per-day quota does not smooth out: there is no burst allowance to borrow against, and the counter is the same whether the agent made one large query or five hundred small ones.
- The API key is per user, taken from Integrations → Fireflies API, so the agent sees exactly the meetings that one person can see and loses them all when that person leaves.
- There are no scope tokens to request. The bearer key is the whole grant, which is why the docs lean on "never expose it in client-side code" rather than on least privilege.
- Event subscriptions are a separate Webhooks V2 surface, so polling the GraphQL API for new transcripts burns the daily quota that webhooks would not.
Checked against Limits (2026-09-29), Authorization (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Fireflies.ai behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.