TL;DR: Fireflies has one of the most configurable Salesforce integrations of any recorder: notes and summaries log to Contacts, Leads, Opportunities, or Accounts; action items become Tasks; and — unusually — it can save the full transcript into Salesforce (Pro plan+) and even create Leads for unknown participants. The tradeoff is a configuration surface where the defaults matter a lot.
Most recorder-CRM integrations are opinionated: one object, one matching rule, take it or leave it. Fireflies went the other way — its Salesforce integration is a configuration wizard with real choices. That’s power, and it’s also how teams end up with a thousand Tasks attached to a contact named Fred. Verified against Fireflies’ setup guide.
What it can do (more than most)
- Log meeting notes and summaries — with a link to the full transcript — under Contacts, Leads, Opportunities, or Accounts, your choice.
- Optionally create a Salesforce Event per meeting and push action items as Tasks.
- Save the full transcript into Salesforce (requires Fireflies Pro or higher) — rare in this category; most competitors link out.
- Create Leads for unknown participants, or restrict logging to existing records only.
- Run multiple configurations, test with a sample record, and (on Business+) use Integration Rules to filter which meetings sync at all.
Plans: Pro is $10/seat/mo annual, Business $19 (current pricing); Salesforce needs REST API access (Enterprise/Unlimited/Performance/Developer).
Setup
app.fireflies.ai → Integrations → Salesforce → Connect (OAuth), then walk the wizard: contact handling, object attachment, events/tasks, summary vs full transcript, and a sample send. Admins can enable it workspace-wide separately. Before you click through: decide the unknown-participant policy (auto-create Leads is bold; existing-records-only is safe) and turn on Integration Rules if you’re on Business — the default is every meeting syncs.
Meet Fred (the failure modes)
- Internal-only calls and Chrome-extension/“Add to Live” recordings log under fred@fireflies.ai — Fireflies’ fallback notetaker contact — instead of real records. Every Fireflies org eventually discovers its Fred archive.
- Notes attach only to open Opportunities — the same closed-opp blind spot as Fathom’s integration, and the same problem for post-sale teams.
- Matching requires the participant’s email to match an existing Contact/Lead (unless auto-create is on) — unmatched calls silently skip.
Where it lands
If you want maximum call data inside Salesforce — transcripts included — Fireflies is arguably the strongest native option at its price, and its bot-based capture works across every meeting platform. What configuration can’t buy: the transcript saved to Salesforce is still an unread blob on one record. Nothing connects Tuesday’s call to the support tickets, last quarter’s commitments, or the renewal — and no rep is reading 40,000 characters of transcript before the next call. Noded ingests Fireflies (and the rest of your stack) into the Customer Context Graph, where transcripts get distilled once and joined to everything else the account touches — so the answer to “what’s going on with this customer?” takes a question, not an excavation. Keep the native sync for the CRM record of truth; add the graph when you need the memory.
FAQ
Can Fireflies save full transcripts in Salesforce?
Yes — on Pro or higher, via the setup wizard toggle. Most competing recorders only sync a link.
What is the Fred contact?
fred@fireflies.ai — the fallback record where internal-only calls and Chrome-extension recordings get logged when there’s no matched customer contact.
Can I control which meetings sync?
Yes, with Integration Rules — but they require the Business plan ($19/seat/mo annual) or higher. Below that, everything syncs.