Resources · Make integration

Fireflies.ai Make integrationAutomate Fireflies.ai with Make.

Your meeting transcripts can leave Fireflies.ai on their own. The Fireflies.ai Make integration gives you 3 modules: 2 actions and 1 search. This guide shows how to link your account with an API key, then walks you through a first scenario that fetches transcripts.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Fireflies.ai Make integration do for you?

The Fireflies.ai Make integration lets Make read the transcripts stored in your Fireflies.ai account and hand them to the rest of your stack. You build a scenario, which is the automation itself: a chain of modules, each one a brick that does a single job. Fireflies.ai brings three of those bricks, all focused on getting transcripts out.

A transcript archive you control. Start with List Transcripts to see every transcript your user can access, then pass each one to Get a Transcript and store the result wherever your team keeps its records, such as a base described on the Airtable Make integration page.

Sales calls that update the CRM. A sales team can pull the transcript of a prospect call with Get a Transcript and attach it to the matching contact in its CRM, so nobody pastes notes by hand after the call.

Custom data for the curious. When the two ready-made modules don't return what you need, Execute a GraphQL Query sends your own authorized query straight to Fireflies.ai.

Know the limits before you start. Fireflies.ai has no trigger in Make, so nothing fires the moment a meeting ends: your scenario starts on its schedule or from another app's event. There is no Make an API Call module either. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick, and the Make training covers the editor from scratch.

Connect

How do you connect Fireflies.ai to Make?

  1. 01

    Copy your Fireflies.ai API key

    Log in to Fireflies.ai and click Integrations in the left sidebar. In the list of apps, open Fireflies API and copy the API key shown there. The Fireflies.ai help asks you to store it in a safe place, since Make will need it in the next step.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any Fireflies.ai module and click Create a connection. A connection is your Fireflies.ai account linked to Make once, then reused by every Fireflies.ai module. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Make asks you to authenticate and confirm access, accept it. The module is now ready, and every other Fireflies.ai module will offer the same connection in its list.

First scenario

Build your first scenario with Fireflies.ai

GoalWhen Make runs on its schedule, it lists your Fireflies.ai transcripts and fetches the full content of each one.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. Search for Fireflies.ai and pick List Transcripts as your first module.

  2. 02

    Link your account

    Click Create a connection and paste your API key, or pick the connection you already made. Fill the module settings; Make shows the options it can read once the account is linked.

  3. 03

    Add Get a Transcript

    Click the + on the right of the first module and add Get a Transcript. Map the transcript coming from List Transcripts so that each bundle, one transcript per item, gets fetched in full.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; read the bundles each module received and check that the transcripts look right.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. List Transcripts returns all your transcripts on each run, and every bundle uses operations, the unit Make counts on your plan.

Modules

What the Fireflies.ai modules do

Fireflies.ai gives you 3 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

2 modules
Fireflies.ai1

Get a Transcript

Action

In MakeRetrieves a single transcript.

You get the full content of one meeting transcript, ready to send to a document, a CRM record or a message in the next module of your scenario.

When to use it
right after List Transcripts or another module that tells you which transcript you want, so you fetch that one meeting and nothing else.
Watch out
it works on a single transcript per run of the module, so each transcript you fetch costs one operation.
Fireflies.ai2

Execute a GraphQL Query

Action

In MakePerforms an arbitrary authorized GraphQL query.

This module opens the door to data the other two modules leave out: you write your own GraphQL query and Fireflies.ai answers it with your account's permissions.

When to use it
when neither List Transcripts nor Get a Transcript returns the piece of information your scenario needs.
Watch out
the query is yours to write and test, so start with Run once and read the returned bundle before mapping anything further.

Searches

1 module
Fireflies.ai3

List Transcripts

Search

In MakeLists all transcripts available to a user.

Think of it as your inventory: it returns every transcript available to your Fireflies.ai user, each one as a separate bundle that later modules process one by one.

When to use it
at the start of a scenario that archives or sorts meetings, before Get a Transcript fetches each one.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which adds operations.
Need help

Need help automating Fireflies.ai with Make?

A person reads every message.

FAQ

Fireflies.ai and Make: frequent questions

01Is the Fireflies.ai Make integration free?
Yes, Fireflies.ai is a standard app in Make, so you can use it on the Free plan. That plan has its limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. You still need your own Fireflies.ai account for the API key.
02What do you need to connect Fireflies.ai to Make?
A Fireflies.ai account and its API key. In Fireflies.ai, click Integrations in the left sidebar, open Fireflies API and copy the key. In Make, add any Fireflies.ai module, click Create a connection, give it a name if you want, paste the key in the API Key field and click Save. If Make asks you to authenticate and confirm access, accept. The connection is created once and every Fireflies.ai module in your scenarios reuses it, so you only paste the key a single time.
03Does Fireflies.ai trigger Make scenarios in real time?
No. The Fireflies.ai app has no trigger module in Make, scheduled or instant, so Fireflies.ai cannot start a scenario by itself. You have two ways to begin anyway. The first is the schedule: the clock on the first module runs the scenario every 15 minutes by default, and List Transcripts can open the flow. The second is another app's trigger placed before the Fireflies.ai modules, so an event in that app starts the run and the Fireflies.ai modules take over from there.
04What if a Fireflies.ai module is missing in Make?
Start with Execute a GraphQL Query. It sends an authorized GraphQL query of your choice to Fireflies.ai, which covers data that List Transcripts and Get a Transcript leave out. The app has no Make an API Call module, so this query module is your only way beyond the ready-made ones. Test the query with Run once and read the bundle before building on it. If you are stuck or need a more complex flow, the team behind this site builds Make scenarios for clients and can help.
05Should you use Make or n8n for Fireflies.ai?
It depends on the tool you already use. On Make, Fireflies.ai gives you 3 modules, a connection by API key and access from the Free plan, which this page covers step by step. The same app often has an n8n node as well, so check that side before you decide. Neither choice is ranked here: pick the one your team already knows, then compare the modules each offers for your case. The n8n vs Make comparison on this site goes through the general differences between the two tools.