# Fireflies.ai integrations: transcripts

> Add the bot to a meeting and create a bite in Fireflies.ai, and start a workflow when Fireflies.ai sends “Meeting transcribed”.

**Canonical page:** https://tray.ai/connectors/fireflies-integrations/
**Categories:** AI
**Connects through:** HTTP Connector

## Overview

Fireflies.ai records, transcribes and summarises meetings, then lets teams search, share and analyse what was said. Tray.ai connects to Fireflies.ai through the HTTP Connector, so your workflows can call the Fireflies.ai API alongside the rest of your stack.

## Use cases

### Transcripts

Read and delete transcripts in Fireflies.ai from any Tray.ai workflow. The Fireflies.ai API covers calls such as list transcripts and get a transcript.

- List transcripts
- Get a transcript
- Delete a transcript

### Meetings

Create and update meetings in Fireflies.ai from any Tray.ai workflow. The Fireflies.ai API covers calls such as upload meeting audio and add the bot to a meeting.

- Upload meeting audio
- Add the bot to a meeting
- Update a meeting title

### Users

Read and update users in Fireflies.ai from any Tray.ai workflow. The Fireflies.ai API covers calls such as list users and get a user.

- List users
- Get a user
- Set a user role

### User groups

Read, create, and delete user groups in Fireflies.ai from any Tray.ai workflow. The Fireflies.ai API covers calls such as list user groups and add a user to a group.

- List user groups
- Add a user to a group
- Remove a user from a group

### Bites

Read and create bites in Fireflies.ai from any Tray.ai workflow. The Fireflies.ai API covers calls such as list bites and get a bite.

- List bites
- Get a bite
- Create a bite

### Channels

Read channels in Fireflies.ai from any Tray.ai workflow. The Fireflies.ai API covers calls such as list channels and get a channel.

- List channels
- Get a channel

## Challenges Tray.ai solves

### Keeping Fireflies.ai credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Fireflies.ai credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Fireflies.ai API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Fireflies.ai API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Fireflies.ai?

Yes. Tray.ai connects to Fireflies.ai through the HTTP Connector, which calls the Fireflies.ai API directly. Any call the Fireflies.ai API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Fireflies.ai?

The Fireflies.ai API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Fireflies.ai connector?

Fireflies.ai runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Fireflies.ai connector from the Fireflies.ai API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/