Closed beta: The Fireflies connection is part of the Conversations closed beta and is available only on selected portals. Contact support@productlift.dev if you want access.
How to get there: Go to Settings → Integrations, then expand Fireflies below HubSpot.
The Fireflies integration sends completed meeting transcripts to ProductLift automatically. ProductLift extracts feature requests and emails the call owner when decisions are ready, so nobody has to copy and paste transcripts after each call.
You need:
The Fireflies account behind the API key determines which transcripts ProductLift can fetch. Fireflies documents that a Super Admin API key can access all meetings in the workspace, while a regular user's access is narrower.
In Fireflies, open Settings → Developer settings and copy the API key. Fireflies also exposes this through Integrations → Fireflies API → Get API Key. See Fireflies' API key guide if the location has changed.
Keep the key private. Anyone with it may be able to retrieve meeting data available to that Fireflies user.
Saving once generates a portal-specific webhook URL and signing secret.
meeting.transcribed.The ProductLift webhook URL includes an unguessable portal token. ProductLift also verifies the Fireflies signature with the signing secret before accepting a delivery.
After Fireflies sends a test or completed-meeting webhook, ProductLift shows Last webhook received in the Fireflies card. This confirms delivery reached ProductLift. It does not by itself confirm that a transcript contained feature requests.
When the call contains requests to review, the matched call owner receives one ProductLift email with a link to the conversation.
Use Import last 30 days to bring in recent transcripts that existed before you configured the webhook.
ProductLift first previews:
Confirm the preview to queue the new calls. Every conversation uses at least one AI credit, and matching extracted requests can use additional credits. The import is refused when your current balance cannot cover at least the extraction credit for every new conversation.
ProductLift uses the portal's Product Vision and the transcript itself to decide whether a call belongs to the product. Calls about another product are filed under Conversations → Not this product instead of entering the review inbox.
This classification still uses one AI credit because ProductLift must read the call to make the decision. ProductLift does not currently offer a title-keyword filter before processing, and meeting titles generated by Fireflies are not reliable enough to use as the only routing rule.
For the cleanest separation and lowest credit usage, connect an API user or Fireflies workspace whose meeting access is limited to the relevant product whenever that is practical.
ProductLift uses Fireflies meeting metadata as follows:
Review the full workflow in Turn customer conversations into reviewed feature requests.
The signing secret does not match, or the signature is missing. Copy the current signing secret from ProductLift into the Fireflies webhook configuration.
The webhook reached ProductLift but did not contain the expected meeting.transcribed event and meeting ID. Confirm that the Fireflies webhook sends the transcription-completed event, not a different meeting event.
ProductLift first matches the Fireflies organizer email, then the host email, to a portal admin. When neither matches, it falls back to the account owner or another admin. Make sure the admin uses the same email address in both products.
Turn off Enable Fireflies import and click Save. New webhook deliveries will no longer import conversations. Existing conversations, approved posts, sources, customers, and votes remain in ProductLift.