Integrations · Fireflies
Guild agents query your Fireflies meeting data and upload audio recordings without your API key ever leaving Guild’s servers. Credentials are injected server-side by Guild’s credential proxy, and credential policies let you restrict exactly which operations each agent can run. Every request is governed before it reaches Fireflies.
Book a demo
See how teams govern agents that use Fireflies.
Talk to sales
Get access to Guild, then connect Fireflies to your first agent.
What the Fireflies integration exposes
The integration provides a GraphQL tool that runs queries and mutations against the Fireflies API. Agents can retrieve meeting transcripts, summaries, action items, speaker information, user data, and bites, and can upload audio recordings. All operations go through the singlefireflies_graphql_query tool. Use pick() to give an agent access to only that tool and nothing else from your tool set.
How it works
1
Get your Fireflies API key
In Fireflies, open Integrations and find the API section to generate your API key.
2
Connect the credential in Guild
Go to Access & setup > Credentials, click Connect, select fireflies, and paste the key into the API Key field. Guild stores it and sends it as a bearer token in the Authorization header on every request.
3
Add FirefliesTools to your agent
Import
FirefliesTools from @guildai-services/guildai~fireflies and spread it into your agent’s tools object. Use pick() from the SDK tools page to include only what the agent needs.Why Fireflies access needs governing
Meeting transcripts and summaries contain sensitive conversations. Guild’s credential proxy holds the Fireflies API key server-side so agent code, prompts, and containers never see it. You can scope a credential to a single workspace, a single member, or one specific agent, keeping shared credentials away from workspaces that should not reach them. See Credentials for the full scoping options. Credential policies add a second layer. You write ALLOW and DENY rules that the proxy enforces before any GraphQL request leaves Guild. A DENY rule blocks a request even when an ALLOW rule also matches. Rules can be scoped to specific agents or workspaces, so one agent can run read queries while another is blocked from mutations on the same credential. Without a scoped policy the credential starts with an allow-all default; delete that default once your rules cover everything agents should reach. See Credential policies for rule syntax and enforcement details.About the Fireflies integration
Agents can run GraphQL queries and mutations against the Fireflies API to retrieve meeting transcripts, summaries, action items, and speaker information. They can also access user and bite data or upload audio recordings. Authentication requires a Fireflies API key. The integration isguildai~fireflies.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Fireflies
In Guild, go to Access & setup > Credentials, click Connect, select fireflies, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thefireflies_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~fireflies:
Frequently asked questions
Can a Guild agent upload audio to Fireflies?
Can a Guild agent upload audio to Fireflies?
Yes. The
fireflies_graphql_query tool runs mutations as well as queries, so an agent can submit an audio upload mutation against the Fireflies API.Does my Fireflies API key go into the agent code?
Does my Fireflies API key go into the agent code?
No. Guild’s credential proxy injects the key as a bearer token in the Authorization header server-side. The key never appears in agent code, prompts, or state.
Can I limit which GraphQL operations an agent is allowed to run?
Can I limit which GraphQL operations an agent is allowed to run?
Yes. Write ALLOW and DENY rules in a credential policy scoped to that agent. A matching DENY rule blocks the request before it reaches Fireflies, regardless of any ALLOW rules.
Does the Fireflies integration receive webhook events from Fireflies?
Does the Fireflies integration receive webhook events from Fireflies?
Not yet. The catalog entry lists no webhook events for this integration, so agents cannot react to Fireflies events via event triggers at this time.
Put a governed agent on Fireflies this week
Book a demo
See how teams govern agents that use Fireflies.
Talk to sales
Get access to Guild, then connect Fireflies to your first agent.