Fireflies APIConnect Fireflies without building on its API
Fireflies has a GraphQL API. Self-serve on every plan (Free, Pro, Business, Enterprise), with throughput set by plan. If you're reading the docs because you need Fireflies to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Fireflies and your other tools.
- APIGraphQL
- AuthAPI key
- AccessSelf-serve
What the Fireflies API gives you
- Type
- GraphQL
- Authentication
- API key (Bearer token)
- Who can get access
- Self-serve on every plan (Free, Pro, Business, Enterprise), with throughput set by plan.
- What it covers
- Meeting transcripts, summaries, users, and live meeting bot controls (Add to Live).
- Limits
- 50 requests/day on Free, 500/day on Pro, and 60/min on Business/Enterprise.
Official docs: docs.fireflies.ai. Checked September 2026. Vendors change access terms, so confirm with Fireflies before you build.
Building on the Fireflies API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Fireflies credentials, and manage tokens and refreshes. | Connect your Fireflies account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Fireflies task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Fireflies work off someone's desk, the build is the slow part.
What teams usually want the Fireflies API for
Notes to CRM
Caddi captures the Fireflies meeting summary and logs it to the contact in Salesforce.
Create follow-up tasks
Caddi turns Fireflies action items into follow-up tasks in Outlook.
Share the summary
Caddi posts the right Fireflies meeting summary to the channel.
Fireflies API questions
Does Fireflies have an API?
Yes. Fireflies has a GraphQL API, authenticated with API key (Bearer token). The official documentation is at https://docs.fireflies.ai/.
How do I get access to the Fireflies API?
Self-serve on every plan (Free, Pro, Business, Enterprise), with throughput set by plan.
Does the Fireflies API have rate limits?
50 requests/day on Free, 500/day on Pro, and 60/min on Business/Enterprise.
Can I connect Fireflies to my other tools without writing code against its API?
Yes. With Caddi you show the Fireflies task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Fireflies and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Fireflies with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Fireflies is reviewed before it runs in production, and every run is logged.
Connect Fireflies without the build.
Drop your work email and pick a time. We'll show you Caddi running your Fireflies workflow end to end.