How RevOps Teams Configure Fireflies.ai CRM Integrations for Salesforce and HubSpot

Revenue Operations (RevOps) teams configure Fireflies.ai CRM integrations to solve pipeline lag and data drop-off caused by manual sales note-taking. When configured correctly, Fireflies automatically matches meeting participants to existing CRM records by email domain, creates timeline events and tasks, associates notes with active deals or opportunities, and uses AI prompts via CRM Autofill to update structured fields without manual data entry.

Achieving reliable CRM automation requires moving beyond basic personal connections. RevOps leaders must establish workspace-level admin governance, implement strict domain-matching filters to prevent database pollution, define field-level write behaviors (Append versus Overwrite), and implement a human-in-the-loop review workflow.

1. Architectural Overview and Matching Logic

The integration between Fireflies.ai and CRMs (Salesforce and HubSpot) operates on a post-call event architecture. Once a meeting recorded by the Fireflies notetaker concludes, the audio is processed into a full transcript, an AI summary, and action items. Fireflies then triggers an outbound API sync based on preconfigured workspace rules.

+-------------------------------------------------------------------+
|                        Fireflies.ai Engine                        |
|  [Meeting Audio / Transcript] -> [AI Summary] -> [Action Items]   |
+---------------------------------+---------------------------------+
                                  |
               Post-Call Webhook / Sync Processing
                                  |
                                  v
+-------------------------------------------------------------------+
|                        Participant Parser                         |
|   1. Extract attendee emails & domain names                       |
|   2. Check Integration Rules (External vs. Internal filter)       |
+---------------------------------+---------------------------------+
                                  |
            +---------------------+---------------------+
            |                                           |
            v                                           v
+-----------------------+                   +-----------------------+
|  Salesforce Matching  |                   |   HubSpot Matching    |
| - Match Lead/Contact  |                   | - Match Contact/Lead  |
| - Relate to Account   |                   | - Relate to Company   |
| - Attach Opportunity  |                   | - Attach Deal/Stage   |
| - Task / Event Log    |                   | - Task / Call / Note  |
| - Custom Field Fill   |                   | - CRM Autofill Props  |
+-----------------------+                   +-----------------------+

Identity and Association Resolution

1. Attendee Email Matching: Fireflies parses the email addresses of all calendar invite participants. It queries the CRM for matching Contact or Lead records.
2. Company/Account Association: Once a Contact or Lead is resolved, Fireflies uses CRM relationships or email domain matching to associate the meeting with the parent Account (Salesforce) or Company (HubSpot).
3. Pipeline (Opportunity / Deal) Association:
   • In Salesforce, Fireflies can automatically link meeting notes to open Opportunities tied to the matched Contact or Lead.
   • In HubSpot, RevOps admins can define the target Deal Pipeline and specific Deal Stages (such as Appointment Scheduled or Qualified to Buy) where meeting logs must be attached.
4. Safety Defaults: If a participant does not exist in the CRM, RevOps can restrict Fireflies to log notes under existing records only, avoiding clutter from personal email domains or external vendors. Alternatively, orphan meetings can be routed to the Fireflies notetaker record (fred@fireflies.ai).

2. Prerequisites and License Requirements

Before configuring integrations, RevOps teams must confirm required plan tiers and API permissions across systems:

3. Configuring the Salesforce Integration

Setting up Salesforce requires authenticating via OAuth 2.0, establishing record matching parameters, and activating opportunity linking.

Step 1: Connect Fireflies to Salesforce

1. In the Fireflies admin dashboard, navigate to Integrations in the left sidebar.
2. Select Salesforce and click Connect.
3. Authenticate with your Salesforce admin credentials and grant the requested OAuth REST API permissions.

Step 2: Configure Contact and Lead Matching

RevOps teams must choose how Fireflies behaves when encountering new or unrecognized meeting attendees:

• Log notes under existing Contacts/Leads only: Enable this toggle (ON). When enabled, Fireflies only syncs notes if a matching Contact or Lead exists in Salesforce. Unmatched external meetings will not create ghost records.
• Create Leads instead of Contacts: If your organization uses an outbound SDR model where reps meet prospects not yet in Salesforce, keep this enabled to capture net-new records as Leads rather than Contacts.
• Log notes under Fireflies Notetaker (fred@fireflies.ai): Use this fallback so internal or unassociated meetings remain searchable without attaching to client accounts.

Step 3: Configure Activity Logging and Opportunity Attachment

Decide how conversation data appears within Salesforce record timelines:

• Create Events: Creates a standard Salesforce Event in the record's Activity History.
• Create Tasks: Converts Fireflies AI-detected Action Items into Salesforce Tasks assigned to the meeting owner.
• Attach Meeting Notes to Opportunities: Automatically attaches the meeting summary and notes to active, open Opportunities associated with the matched Contact.
• Attach Meeting Notes to Accounts: Ensures full conversational visibility at the parent account level for cross-functional visibility (Customer Success and Account Management).

Step 4: Meeting Output and Verification

• Enable Save meeting summaries and Save meeting transcripts.
• Click Send Sample to verify that test data populates cleanly in your Salesforce sandbox or production environment before enabling live synchronization.

4. Configuring the HubSpot Integration

The HubSpot connector offers bidirectional functionality, supporting both post-meeting logging and inbound call transcription through the HubSpot Dialer.

Step 1: Connect and Authorize

1. Navigate to Integrations > HubSpot in Fireflies.
2. Click Connect, select your target HubSpot portal, and approve app installation permissions.

Step 2: Select Action Mode

Fireflies offers two operational paths for HubSpot:

1. Send meeting data to HubSpot: Standard mode for logging video conference meetings (Zoom, Google Meet, Microsoft Teams) to HubSpot records.
2. Pull recordings from HubSpot: Designed for teams utilizing HubSpot's native calling tool. In this mode, Fireflies imports completed calls based on Transcribable Call Outcomes (such as Connected, Meeting booked, or Left live message) to generate transcripts and summaries.

Step 3: Participant Management and Company Mapping

• Set Send output to Contacts and Send output to Leads based on your sales architecture.
• Turn on Only log meeting data if contact/lead already exists in CRM to preserve CRM cleanliness.
• Enable Also log meeting notes to company to link conversations directly to target accounts.

Step 4: Pipeline and Deal Association

To anchor sales calls to revenue pipeline:

1. Under Pipeline Integration, toggle on deal logging.
2. Select your target Deal Pipeline (for example, Enterprise Sales or New Business).
3. Select the eligible Deal Stage (for example, Qualified to Buy or Demo Completed). Fireflies queries deals matching the attendee's contact record within those designated stages and attaches the meeting log.

Step 5: Activity Types and HubSpot App Cards

• Choose whether Fireflies logs as a combined Call and Note or as Note only.
• Enable Create tasks from meeting action items to populate HubSpot's task queue.
• Embed Fireflies App Cards: In HubSpot, customize record views for Contacts and Companies by adding the Fireflies App Card. This allows reps to listen to meeting soundbites, view AI sentiments, and read summaries directly within the HubSpot interface.

5. Setting Up CRM Autofill for Custom Field Updates

Standard integration pushes unstructured notes into timelines. For RevOps teams enforcing qualification methodologies (such as MEDDPICC, BANT, or SPICED), unstructured text does not support reporting. Fireflies CRM Autofill extracts structured answers from the transcript and populates standard and custom CRM properties.

+-------------------------------------------------------------------------+
|                       CRM Autofill Configuration                        |
+-------------------------------------------------------------------------+
| CRM Target Property        | Extraction Prompt            | Write Rule  |
|----------------------------+------------------------------+-------------|
| Deal: Next Steps           | "Extract the immediate next  | 🔄 Overwrite|
|                            | step agreed upon by both     |             |
|                            | parties."                    |             |
|----------------------------+------------------------------+-------------|
| Contact: Pain Points       | "Identify the key business   | 📄+ Append  |
|                            | challenges discussed."       |             |
|----------------------------+------------------------------+-------------|
| Deal: Competitor Mentions  | "Extract competitor names    | 📄+ Append  |
|                            | mentioned by the prospect."  |             |
|----------------------------+------------------------------+-------------|
| Deal: Target Go-Live Date  | "Identify the requested or   | 🔄 Overwrite|
|                            | planned deployment date."    |             |
+-------------------------------------------------------------------------+

Configuration Steps

1. Navigate to Integrations > HubSpot (or Salesforce) > Setup Autofill.
2. Select target objects: Contacts, Companies/Accounts, or Deals/Opportunities.
3. Add Custom Field:
   • Ensure the property already exists in your CRM schema.
   • Choose the target CRM property from the dropdown.
   • Define Insight Prompt: Write a precise instruction. Rather than writing "Budget", write: "Extract the specific dollar amount or budget range mentioned by the prospect for this initiative."
   • Fireflies automatically aligns the extracted value with the CRM property type (Text, Date, Numerical).
4. Set Write Behavior (Append vs. Overwrite):
   • Append (📄+): Concatenates newly extracted insights to existing field values without deleting history. Use this for rolling notes, pain points, competitor evaluations, and technical objections.
   • Overwrite (🔄): Replaces old field contents with the latest conversation output. Use this for single-state operational fields such as Next Step Summary, Next Step Date, Economic Buyer Identified, or Current Deal Stage Notes.

The Human-in-the-Loop Review Gate

To maintain data integrity, CRM Autofill does not overwrite CRM fields silently in the background:

1. When a call concludes, Fireflies spends 1 AI credit to extract values for your configured fields.
2. An Autofill CRM banner appears at the top of the meeting notepad in Fireflies.
3. The sales rep or RevOps analyst clicks Review, inspects the drafted values, edits or unchecks any discrepancies, and clicks Send to CRM.
4. For older meetings, reps can run Autofill CRM On Demand directly from the transcript integration tab.

6. Workspace Governance, Rules Engine, and Team Deployment

Individual rep configurations lead to conflicting CRM updates. RevOps administrators must manage the rollout centrally.

RevOps Integration Setup Checklist
├── Step 1: Pre-Configuration Audit
│   ├── Create custom fields in Salesforce / HubSpot (e.g., MEDDPICC, Next Steps)
│   └── Verify REST API permissions and Admin account access
├── Step 2: Global Security & Sync Policies
│   ├── Navigate to Fireflies Settings > Team > Integration Permissions
│   ├── Enable: Apply configuration to all users who have access
│   └── Enable: Restrict non-admin usage
├── Step 3: Rules Engine Filtering
│   ├── Rule 1: Meeting Type EQUALS "External"
│   ├── Rule 2: Title DOES NOT CONTAIN "Internal, 1:1, Sync, Standup"
│   └── Rule 3: Participant Domain DOES NOT CONTAIN company internal domains
├── Step 4: Pilot Group Testing
│   ├── Roll out to 3-5 Account Executives
│   ├── Execute Send Sample tests
│   └── Validate Append vs. Overwrite behavior on live Opportunities
└── Step 5: Full Rollout & On-Demand Backfill
    ├── Enable team-wide sync
    └── Run Push Past Meetings for in-flight deals (Last 14-30 days)

Integration Rules Engine

Available on Business and Enterprise plans, the Rules Engine filters out non-sales conversations before they trigger CRM syncs:

• Meeting Type Filter: Set rule to Meeting Type = External to block all internal standups and company meetings.
• Title Filters: Add conditions such as Title Contains: Demo, Discovery, Evaluation, Review and Title Doesn't Contain: 1:1, Sync, Planning.
• Host / Participant Logic: Combine conditions with AND / OR operators (for example, Host equals sales-team@company.com AND Participant is External).

Workspace-Wide Policy Enforcement

1. Go to Settings > Team > Integration Permissions.
2. Locate Salesforce or HubSpot and click Manage.
3. Under Sync Preference, toggle on Apply configuration to all users who have access. This forces every workspace member to inherit standardized field mappings and rules.
4. Toggle on Restrict non-admin usage to prevent individual reps from modifying field mappings or disabling sync filters.

Historical Backfilling (Push Past Meetings)

When onboarding an existing team with deals in progress:

1. Open the integration settings and select Push past meetings.
2. Choose a date window (Last 7, 14, 30, 60, or 90 days).
3. Select eligible meetings (Meetings I attended or All my meetings) and execute the push. Fireflies retrospectively logs past discussions and action items against active pipeline records.

7. Comparative Architectural Matrix: Salesforce vs. HubSpot

8. RevOps Best Practices and Troubleshooting

1. Avoid Overwrite on Chronological Fields: Never set fields like Customer Challenges or Objections to Overwrite. Subsequent short check-ins or scheduling calls will wipe detailed discovery notes from earlier meetings.
2. Deterministic Extraction Prompts: When writing AI Autofill prompts, provide negative constraints. Example: "Extract the target contract sign date discussed. If no specific date was discussed, output None. Do not infer dates."
3. Prevent Contact Flooding: Ensure Log notes under existing Contacts/Leads only is kept ON unless reps explicitly manage initial inbound capture through Fireflies. Otherwise, external partners, interview candidates, and vendors will generate extraneous records in your CRM.
4. Review Habit Coaching: Embed the Autofill review step into the sales team's post-call workflow. Reps should open the Fireflies Notepad immediately after calls, review drafted CRM properties in the review banner, confirm accuracy, and push the update. This guarantees high pipeline hygiene without taking reps away from selling.

References

• How to set up Salesforce and Fireflies integration | Fireflies Knowledge Base
• How to Integrate HubSpot with Fireflies | Fireflies Knowledge Base
• How to save meeting notes under Salesforce Opportunities
• Integration Permissions: Control Who Can Access and Connect Integrations
• Fireflies Business tier pricing and features | Fireflies Knowledge Base