EQALL + Fireflies.
Connect EQALL to Fireflies with an API key and a Meeting Transcribed webhook. As soon as Fireflies finishes transcribing a call, the transcript flows into EQALL and becomes Meeting Minutes, Summary, Sentiment, Opportunities, Action Items, and Follow Up Emails.
What this integration does
The Fireflies integration combines two mechanisms. EQALL uses your Fireflies API key to authenticate, and Fireflies pushes a signed webhook to EQALL every time a meeting finishes transcribing. The signed-payload model means EQALL can verify that incoming data is genuinely from Fireflies, not spoofed.
| Fireflies | Flow | EQALL |
|---|---|---|
| Meeting Transcribed event (webhook) | → | Real-time transcript ingestion |
| Transcript content (via API) | → | Meeting Minutes |
| Speaker labels | → | Attendee context |
| Meeting metadata | → | Meeting records |
From this data, EQALL generates Summary, Sentiment, Opportunities Identified, Action Items with owners and due dates, and Follow Up Emails you review and send. EQALL only reads from Fireflies, it does not modify your Fireflies recordings or transcripts.
Get Started with EQALL
If your team is new to EQALL, complete these steps first. Setup takes about five minutes.
Go to eqall.com/en/register/login or download EQALL from the App Store. Select Sign in with Google or Microsoft using your company email. Allow all permissions for the best experience.
Complete a one-time LinkedIn sign-in to enrich attendee profiles with relationship context, communication styles, and deal-specific insights.
Go to Avatar Image → Products & Services and review what EQALL has pre-populated. This powers your personalized insights and deal recommendations. You can edit, add, or delete products by providing a company website, an uploaded file, or entering details manually.
Go to Settings → Notifications and turn on Today at a Glance and Meeting Summary to stay on top of every deal.
Connecting EQALL to Fireflies
The Fireflies setup has two parts. Part A configures EQALL to read from Fireflies. Part B configures Fireflies to push transcripts to EQALL. Keep both EQALL and Fireflies open in separate browser tabs.
Part A. Add the Fireflies API key in EQALL
Go to Avatar → Settings → Integrations → Collaboration → Fireflies and click Connect. EQALL displays three fields: API Key, Webhook URL, and Secret Key. Leave this page open.
In a new tab, sign in to Fireflies and go to app.fireflies.ai/settings/developer-settings. Copy your API Key.
Return to the EQALL Fireflies integration page and paste the key into the API Key field.
Part B. Configure the Fireflies webhook
Go to app.fireflies.ai/integrations/api/webhook and click + Add Config. Click on Configuration # at the top of the new config and rename it to EQALL.
Copy the Webhook URL shown on the EQALL Fireflies integration page and paste it into the Webhook URL field in Fireflies.
In EQALL, click the wand icon next to the Secret Key field to generate a new key, then click the copy icon. In Fireflies, paste the value into the Signing Secret field.
Click on Search in the event picker and select Meeting Transcribed. This tells Fireflies to fire the webhook to EQALL every time a meeting transcript becomes available.
Click Save in Fireflies to activate the webhook config, then click Save in EQALL. EQALL validates the connection and the Fireflies status updates to Connected.
Treat the API Key and the Signing Secret like passwords. The API Key grants read access to your Fireflies data. The Signing Secret is what EQALL uses to verify incoming webhook payloads. If either is exposed, regenerate it in the originating system (Fireflies for the API Key, EQALL for the Secret Key) and reconnect.
How to Use the Integration
Once connected, the Fireflies integration runs across the full meeting lifecycle, mapped to EQALL's PRO framework.
Open the upcoming meeting in EQALL to see attendee profiles, communication style recommendations, commonalities, and a suggested agenda. Use EQALL Rehearse to practice your opener and key questions before the call.
Run your meeting as usual with the Fireflies notetaker capturing the conversation. Recording and transcription are controlled inside Fireflies. As soon as Fireflies finishes processing the transcript, the Meeting Transcribed webhook fires and EQALL ingests the content automatically.
Open the meeting in EQALL to review:
- Meeting Summary and Sentiment
- Opportunities Identified
- Action Items with owners and due dates
- Follow Up Emails you can copy or send using your usual email tool
Update or confirm any generated items and share with your team.
No meeting data appearing? Confirm that Fireflies actually captured and processed the transcript, and that the EQALL webhook config in Fireflies is set to Meeting Transcribed. Fireflies only fires the webhook to EQALL when the transcript is complete.
Remove or Disconnect the Integration
You can disconnect EQALL from Fireflies at any time. For a clean reset, disconnect from both sides.
Go to Avatar → Settings → Integrations → Collaboration → Fireflies and click Disconnect. EQALL deletes the stored API key and stops processing Fireflies webhook events.
Go to the Fireflies Webhooks page and delete the EQALL config so Fireflies stops sending events. Then go to Developer Settings and revoke the API key EQALL was using.
You can reconnect at any time by regenerating an API key and adding a new webhook config in Fireflies.
Setup Checklist
- EQALL account created and signed in with Google or Microsoft
- LinkedIn connected (one-time step)
- Products & Services reviewed and confirmed in EQALL
- Fireflies account with access to Developer Settings
- Fireflies API key pasted into EQALL
- Webhook config added in Fireflies and renamed to EQALL
- EQALL Webhook URL pasted into Fireflies
- EQALL Secret Key generated and pasted into Fireflies Signing Secret
- Meeting Transcribed event selected in Fireflies
- Saved in both Fireflies and EQALL (status shows Connected)
- Notifications enabled (Today at a Glance + Meeting Summary)
Questions or live walkthrough?
Our team will set up the Fireflies integration with you live, or answer any questions about API key management, webhook signing, and security.