> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Query Fireflies transcripts and meeting data from Guild agents

> Connect Guild agents to Fireflies to retrieve meeting transcripts, summaries, action items, speaker data, and upload audio recordings via GraphQL.

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.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Fireflies.

> [card] [Talk to sales](https://guild.ai/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 single `fireflies_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](https://docs.guild.ai/sdk/tools.md) 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](https://docs.guild.ai/platform/credentials.md) 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](https://docs.guild.ai/platform/credential-policies.md) 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 is `guildai~fireflies`.

## Authentication

* **Type:** API key
* **Header:** Guild sends the key as a bearer token in the `Authorization` header

### Setup

**1. Connect Fireflies**

In Guild, go to **Access & setup > Credentials**, click **Connect**, select **fireflies**, and paste the key into **API Key**.

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { FirefliesTools } from "@guildai-services/guildai~fireflies"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You work with Fireflies.",
  tools: { ...FirefliesTools },
})
```

### Selecting specific tools

Tools are named with the `fireflies_` prefix. Use [`pick()`](https://docs.guild.ai/sdk/tools#selecting-specific-tools) to include only what your agent needs.

## Tools

Tools in the latest published version of `guildai~fireflies`:

| Tool | What it does |
| - | - |
| `fireflies_graphql_query` | Run a GraphQL query or mutation against Fireflies. |

## Frequently asked questions

> [accordion] 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.

> [accordion] 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.

> [accordion] Can I limit which GraphQL operations an agent is allowed to run?
>
> Yes. Write ALLOW and DENY rules in a [credential policy](https://docs.guild.ai/platform/credential-policies.md) scoped to that agent. A matching DENY rule blocks the request before it reaches Fireflies, regardless of any ALLOW rules.

> [accordion] 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](https://docs.guild.ai/platform/event-triggers.md) at this time.

## Put a governed agent on Fireflies this week

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Fireflies.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Fireflies to your first agent.

## Related

**Also runs on Guild:** [Calendly](https://docs.guild.ai/integrations/calendly.md) · [Coda](https://docs.guild.ai/integrations/coda-openapi.md) · [Confluence](https://docs.guild.ai/integrations/confluence.md) · [Fathom](https://docs.guild.ai/integrations/fathom.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)