Teams that run Zoom Phone and Salesforce side by side usually discover the same problems within a quarter:
call activity lives in Zoom Phone while deal records live in Salesforce, so reps toggle between tools to connect conversations to pipeline,
contacts created during phone calls never make it into the CRM, leaving gaps in reporting and follow-up,
and when a prospect calls back three times before a rep logs the activity, the signal never reaches the opportunity record.
However, the two platforms ended up coexisting (a sales team choosing Zoom Phone for its communications while the org runs on Salesforce, separate departments adopting different tools, or an IT consolidation putting Zoom Workplace alongside an entrenched CRM), the longer they operate without a connection, the more call data goes untracked and the harder it becomes to tie phone activity to revenue.
Connecting Zoom Phone and Salesforce closes that gap.
Call activity logs flow into Salesforce records automatically so managers can see outbound and inbound call volume without asking reps to update the CRM manually. Inbound calls trigger contact lookups and screen pops so reps know who is calling before they answer.
Click-to-dial from Salesforce contact, lead, and opportunity records eliminates manual number entry so that every call is logged against the right record from the start.
Zoom offers a native Salesforce integration through the "Zoom for Lightning" app, available on the Salesforce AppExchange and the Zoom Marketplace.
For teams needing workflows beyond what the native connector covers, third-party automation tools like Zapier can extend the integration, and custom API development offers full control for complex requirements. Each method differs in setup complexity, sync direction, data coverage, and cost.
There is also one problem no connection method solves: the integration logs calls and syncs activity, but it does not verify whether the contacts those calls are logged against are still accurate, still at the company, or still reachable at the number on file.
And that is where ZoomInfo comes in. ZoomInfo integrates natively with both Salesforce and Zoom Phone, and offers API and MCP access that can feed verified, enriched contact data into either platform, so the records behind every call are accurate and complete before the phone rings.
This article covers the Zoom Phone-Salesforce integration: which methods are available, what data each one handles, how to set them up, the use cases that justify connecting both platforms, and the limitations to plan for. At the end it also covers how ZoomInfo fits into the picture as a data enrichment layer that strengthens the records flowing between Zoom Phone and Salesforce.
Let's start with an overview of the integration.
Integration Overview
Source: Zoom Phone
Does a native integration exist?
Yes. Zoom offers a native Salesforce integration called "Zoom for Lightning," available on the Salesforce AppExchange. It embeds a Zoom Phone dialer widget inside Salesforce, enables click-to-dial, logs call activity automatically, and surfaces Zoom AI call summaries linked to Salesforce records.
What data can sync?
Call activity is the primary sync: inbound and outbound call logs, call duration, call recordings, voicemails, and AI-generated call summaries. Contact matching occurs on inbound calls via caller ID lookup against Salesforce records. Contacts can be created in Salesforce from Zoom Phone when no match exists. SMS activity can also be logged depending on configuration.
Is the sync bidirectional?
Partially. Call activity flows from Zoom Phone into Salesforce automatically. Zoom Phone reads Salesforce contact data for caller identification and click-to-dial, but CRM field updates do not push back into Zoom Phone's contact system. The data flow is primarily Zoom Phone to Salesforce for activity logging, with Salesforce to Zoom Phone for contact lookup.
Is it real-time or batch?
The native integration operates in near real-time. Call logs and activity records appear in Salesforce as calls complete. Click-to-dial and screen pops function in real time during active calls. Third-party automation tools like Zapier trigger within 1 to 15 minutes depending on plan tier.
What are the available methods?
Native Zoom for Lightning integration, third-party automation (Zapier), and custom API development using the Zoom Phone API and Salesforce API.
Method | Setup Difficulty | Data Flow | Real-time? | Cost |
|---|---|---|---|---|
Native (Zoom for Lightning) | Low | Zoom Phone to Salesforce (activity); Salesforce to Zoom Phone (contact lookup) | Near real-time | Included with Zoom Phone plans |
Zapier | Medium | One-way per Zap | Near real-time (1-15 min) | From $19.99/mo |
Custom API | High | Fully customizable | Real-time via webhooks | Developer time + hosting |
One distinction worth settling upfront: the native integration handles both ongoing activity logging and real-time caller identification, making it the only method that covers both jobs in a single setup.
Zapier handles event-triggered flows with narrower data coverage. Custom API development is the only path for teams that need to sync data objects or enforce business logic that neither the native connector nor Zapier supports.
Integration Methods
Native Zoom for Lightning Integration
How it works: Zoom's native Salesforce integration installs as a managed package from the Salesforce AppExchange, embedding a Zoom Phone dialer widget inside the Salesforce Lightning interface. When a rep makes or receives a call through Zoom Phone, the integration matches the phone number against Salesforce records and logs the call as an activity on the matching Lead, Contact, or Account.
Source: Salesforce
Inbound calls trigger a screen pop showing the caller's Salesforce record so the rep has context before answering. Zoom AI call summaries link to Salesforce records after calls complete, giving managers and reps a searchable, structured recap without manual note-taking.
What it syncs: Inbound and outbound call logs (caller, callee, duration, timestamp), call recordings, voicemail records, SMS activity, and AI-generated call summaries. Contact lookup on inbound calls uses Salesforce Lead, Contact, and Account records. When a caller has no matching Salesforce record, the integration can create a new contact automatically.
Fits: ongoing sync of call activity into Salesforce as part of daily sales and service workflows; not a data migration tool.
Setup process:
Install the Zoom for Lightning app from the Salesforce AppExchange. Salesforce System Administrator access is required.
In the Zoom admin portal, navigate to the Marketplace and locate the Salesforce integration. Authorize the connection using OAuth, granting Zoom permission to read Salesforce contact data and write activity records.
Configure which Zoom Phone events should create Salesforce activity records (completed calls, missed calls, voicemails, SMS messages) and set the default record type for logged activities.
Add the Zoom Phone dialer component to the relevant Salesforce Lightning page layouts (Lead, Contact, Account, Opportunity) using the Lightning App Builder so reps can click-to-dial from CRM records.
Set rules for unmatched callers: when an inbound call does not match any existing Salesforce record, choose whether the integration creates a new Lead or Contact automatically.
Test by placing a call from within Salesforce to a known contact and verifying the activity log, recording link, and AI summary appear on the correct record.
Strengths: First-party integration maintained by Zoom and distributed through the Salesforce AppExchange. No third-party tool to configure or pay for separately.
Click-to-dial, automatic call logging, screen pops, and AI call summaries all work within Salesforce Lightning without leaving the CRM. Supports automatic contact creation for unknown callers. AI call summaries eliminate manual post-call note-taking.
Limitations: The sync is primarily one-directional for activity data (Zoom Phone to Salesforce). Custom fields, deal stage updates, and complex CRM workflows are not triggered by the native connector alone.
The integration requires Salesforce Lightning Experience (not available in Salesforce Classic). Setup requires admin access on both platforms. AI call summary features require a qualifying Zoom Workplace paid plan with AI Companion enabled.
Best for: Sales and service teams already using both Zoom Phone and Salesforce that need call activity tracked in the CRM with minimal setup. Teams where reps spend most of their day in Salesforce and want to call from the CRM without switching to a separate dialer application.
Zapier
How it works: Zapier connects Zoom Phone and Salesforce through event-driven automations called Zaps. Each Zap pairs a trigger (an event in one app) with one or more actions (what happens in the other).
Source: Zapier
Zoom Phone events like completed calls, missed calls, new recordings, and new voicemails can trigger actions in Salesforce such as creating Tasks, updating records, or sending notifications. Both platforms are well-supported Zapier connectors, so the available trigger-action combinations cover the major use cases.
What it syncs: Call metadata (caller number, callee number, duration, timestamp, call type), recording URLs, voicemail transcripts, and SMS messages. Each data type requires its own Zap. Custom field mapping is manual and configurable in the Zap setup flow. Zapier does not provide the embedded dialer widget or screen pop functionality that the native integration offers.
Fits: ongoing sync of specific call events into Salesforce workflows; not a replacement for the native integration's real-time dialer features.
Setup process:
Create a Zapier account and connect both your Zoom Phone and Salesforce accounts using OAuth.
Choose Zoom Phone as the trigger app and select the trigger event (e.g., "Call Completed" or "New Voicemail").
Choose Salesforce as the action app and select the action (e.g., "Create Task" or "Update Record").
Map the available fields from the Zoom Phone trigger (caller number, duration, recording URL) into the corresponding Salesforce fields.
Test the Zap with a sample call record to verify the data flows correctly into the expected Salesforce object.
Turn the Zap on. For additional data types (voicemails, SMS, recordings), create separate Zaps for each.
Strengths: No engineering resources required. Quick to set up for use cases the native integration does not cover, such as triggering Salesforce workflows from call events or routing call data to custom objects. Zapier's filter and formatting steps add conditional logic (e.g., only log calls longer than two minutes, or only create records for calls from specific area codes).
Limitations: No embedded dialer, click-to-dial, or screen pop functionality. Each Zap handles one trigger-action pair, so covering multiple call event types requires separate Zaps.
Zapier charges by task count, and high call volumes accumulate costs quickly. Calls made before the Zap was activated do not sync. Latency of 1 to 15 minutes means activity logging is delayed compared to the native integration's immediate sync.
Best for: Teams that already use the native Zoom for Lightning integration but need to trigger additional Salesforce workflows from call events. Teams on Salesforce editions or Zoom Phone plans where the native integration does not cover a specific requirement and a lightweight automation can fill the gap.
Custom API Integration
How it works: Both platforms provide broad APIs. Zoom Phone's REST API covers users, call logs, voicemail, call queues, recordings, SMS, and device management, with webhook support for real-time event notifications.
Source: Zoom Phone
Salesforce's REST API covers all standard and custom objects, with Platform Events and Change Data Capture for event-driven sync. A custom integration connects these APIs directly, with your own middleware handling authentication, field mapping, data transformation, and error recovery.
What it syncs: Anything both APIs expose. This is the only method that supports advanced scenarios like syncing call queue analytics into Salesforce reports, writing Salesforce data back into Zoom Phone user profiles, enforcing business rules during call logging (e.g., routing activity records to specific Opportunity stages based on call outcome), or syncing custom objects that neither the native connector nor Zapier supports.
Fits: either specialized ongoing sync or complex data flows; the only method with no ceiling on customization.
Setup process:
Register API credentials in both platforms: create an OAuth app in the Zoom Marketplace with Phone API scopes, and create a Salesforce Connected App with OAuth 2.0.
Design the data model mapping between Zoom Phone call objects and Salesforce objects, including field-level transformations and a cross-reference table for matching caller IDs to Salesforce records.
Build the sync service: a server-side application that subscribes to Zoom Phone webhooks for call events, transforms the data according to the mapping, and writes activity records to Salesforce via its REST API.
Implement matching logic: look up the caller's phone number against Salesforce Contacts/Leads, decide what to do when no match is found, and handle edge cases like multiple matching records.
Add logging, error handling, and retry logic. Zoom Phone APIs carry reduced rate limits (approximately 50% of standard Zoom API quotas). Salesforce's daily API request allocation starts at 100,000 requests per 24 hours for Professional and Enterprise editions.
Deploy, monitor, and maintain the integration over time.
Strengths: Full control over what syncs, when, and how. Real-time sync via webhooks on Zoom Phone's side and Platform Events on Salesforce's side. Can implement arbitrarily complex business logic, including call routing rules, custom scoring, and multi-object updates. No per-operation fees from a third-party connector.
Limitations: Requires development resources to build and maintain. Zoom Phone webhooks retry failed deliveries only three times (at 5, 20, and 60 minutes), with no guaranteed delivery after that. Zoom's webhook endpoint must respond within three seconds. API changes on either platform require ongoing maintenance. The initial build takes weeks, not hours.
Best for: Organizations with sync requirements that neither the native connector nor Zapier can satisfy. Teams with in-house development resources and complex data models or business logic that must be enforced during call activity logging. Companies that need to pull Zoom Phone analytics data (call queue performance, agent utilization) into Salesforce for consolidated reporting.
Key Use Cases
1. Automatic Call Activity Logging for Sales Reps
Reps make dozens of calls daily through Zoom Phone. Without an integration, each call requires manual logging in Salesforce, and most reps skip it. The native Zoom for Lightning integration logs every call (inbound and outbound) as a Salesforce Task on the matching Contact, Lead, or Opportunity record automatically. Managers get accurate activity metrics without relying on rep discipline.
Best integration method: Native Zoom for Lightning integration.
2. Screen Pops for Inbound Sales and Service Calls
When a prospect or customer calls in, the native integration matches the incoming number against Salesforce records and displays the caller's record before the rep answers. The rep sees the account name, recent opportunities, open cases, and last activity, and can greet the caller by name and start an informed conversation without scrambling to look up the contact mid-call.
Best integration method: Native Zoom for Lightning integration.
3. AI Call Summaries Linked to Opportunity Records
After a discovery call or negotiation, the rep needs a structured summary of what was discussed, what was agreed on, and what the next steps are.
Zoom AI Companion generates post-call summaries automatically, and the native Salesforce integration links those summaries to the relevant Opportunity record. Managers reviewing pipeline can read the AI summary in Salesforce instead of asking the rep to recap the call.
Source: Zoom Phone
Best integration method: Native Zoom for Lightning integration.
4. Triggering Salesforce Workflows from Call Events
A sales process may require specific actions when certain call events occur: a missed call from a high-value prospect should create a follow-up Task, a completed call over 15 minutes should update the Opportunity stage, or a voicemail from a specific area code should notify a regional manager. Zapier handles these conditional, event-driven workflows without engineering resources.
Best integration method: Zapier.
5. Consolidated Call Analytics in Salesforce Reports
Operations teams that need to analyze call patterns (calls per rep, average call duration, time-of-day distribution, call-to-meeting conversion) inside Salesforce's reporting framework can use a custom API integration to pull Zoom Phone call log data into custom Salesforce objects. This lets them cross-reference call data with pipeline and revenue data in a single reporting layer.
Best integration method: Custom API integration.
Limitations and Considerations
Data That Doesn't Sync Natively
The native Zoom for Lightning integration focuses on call activity and contact lookup. It does not sync Zoom Phone system configuration (call queues, auto-attendant settings, user assignments) into Salesforce.
Call queue analytics, agent performance metrics, and detailed routing data require either the Zoom Phone Customer Engagement Pack add-on (which provides its own dashboards) or a custom API build to surface that data in Salesforce. Email thread history, Zoom Meeting recordings, and Zoom Chat messages are separate data streams from Zoom Phone call logs.
Sync Direction Constraints
The integration is primarily one-directional for activity data: Zoom Phone pushes call logs into Salesforce. Salesforce field updates, deal stage changes, and workflow outcomes do not flow back to Zoom Phone.
If a rep updates a contact's phone number in Salesforce, that change does not propagate to Zoom Phone's directory. Teams that need bidirectional data flow will need a custom API integration or a middleware layer.
Pricing Implications
The native Zoom for Lightning integration is included with Zoom Phone plans at no additional cost. However, Zoom Phone's AI Companion features (call summaries, voicemail task extraction) require a qualifying paid Zoom Workplace plan. Zoom Phone plans start at $10/user/month (metered) or $15/user/month (US & Canada unlimited).
On the Salesforce side, API access is included with paid editions, but daily API request allocations (starting at 100,000 for Professional/Enterprise) may constrain high-volume custom integrations. Third-party tools add their own costs: Zapier charges by task count starting at $19.99/month.
Source: Salesforce
Permissions and Access
Setting up the native integration requires admin access on both platforms. In Salesforce, System Administrator access is needed to install the AppExchange package and configure Lightning page layouts.
In Zoom, admin rights are required to authorize the Salesforce connection and configure which call events are logged. If your Salesforce org uses field-level security or sharing rules, the integration user's profile must have write access to the objects and fields where call activity will be stored.
Maintenance
Both platforms update independently. Zoom Phone releases new features on a regular cadence (AI Companion updates, agentic post-call workflows announced for April 2026, new dialer capabilities). Salesforce versions its API with each seasonal release.
The native AppExchange package receives updates from Zoom, but custom configurations (Lightning page layouts, field mappings, workflow rules built on top of call activity data) need periodic review to ensure compatibility. Zapier Zaps may break if either platform changes its API surface or authentication flow.
What No Method Fixes: The Data Itself
Every method above moves call activity from Zoom Phone into Salesforce. None of them checks whether the contact records in Salesforce are accurate, current, or complete. A rep calls a number listed on a Lead record; if that number is disconnected, the call fails, but the integration faithfully logs the failed attempt on a record that was already stale.
A contact who changed jobs three months ago still sits in the pipeline with zero call activity, and there is no way to tell whether that silence means disinterest or a dead number. The integration logs what happens; it does not improve what was there before the call was made.
Where ZoomInfo Fits In
Every method in this guide moves call activity between Zoom Phone and Salesforce. None of them improves the contact data that determines whether a call connects in the first place.
When the integration is live but reps are dialing disconnected numbers, reaching the wrong person because a contact changed roles, or missing direct dials because the CRM only has a main office line, the bottleneck is no longer the connector.
That is the gap ZoomInfo closes.
ZoomInfo is a B2B data and GTM platform built on broad B2B data: 500M contacts, 100M companies, 135M+ verified phone numbers, and 200M+ verified business email addresses. For teams running Zoom Phone calls through Salesforce, ZoomInfo addresses the data quality layer that no call-logging connector handles.
Source: ZoomInfo
ZoomInfo integrates natively with both platforms. The Salesforce integration, available through the AppExchange, provides CRM enrichment, lead routing, and real-time data updates inside Salesforce records. The Zoom Phone integration connects ZoomInfo's data directly to the calling platform.
Source: ZoomInfo
For teams building beyond these native connectors, ZoomInfo's Enterprise API and MCP server expose the same data to any custom agent, internal tool, or partner platform.
Source: ZoomInfo
The same data feeds ZoomInfo's GTM Context Graph, which processes 1.5B + data points daily and combines third-party intelligence with CRM records, conversation transcripts, and behavioral signals to surface not just what happened in a deal, but why.
Source: ZoomInfo
In practice, a team using Zoom Phone for outbound sales through Salesforce can use ZoomInfo to enrich Salesforce records before a rep dials a single number.
Verified direct dials mean calls reach the right person rather than routing through a general switchboard. Accurate job titles mean reps are not pitching someone who moved to a different department. Current employment data means the pipeline does not fill with contacts who left the company two quarters ago.
Buyer Intent data from ZoomInfo, tracking signals from 210 million IP-to-Organization pairings, can prioritize which accounts receive call outreach first, so reps spend dialing time on prospects who are actively researching relevant solutions rather than working through a stale list alphabetically.
Source: ZoomInfo
Enriched records also make the Zoom Phone-Salesforce integration more productive. When call activity logs against records with verified phone numbers and accurate contact details, the ratio of connected calls to total attempts rises. Fewer blank fields mean fewer unmatched inbound calls landing without a screen pop.
And when AI call summaries attach to records that correctly identify the buyer's role, title, and company context, those summaries become useful for deal review rather than annotations on records that may already be wrong.
Seismic's sales team attributed 39% of active pipeline to opportunities identified or influenced by ZoomInfo signals, while boosting productivity by 54% and saving 11.5 hours per week. (Seismic)
Final Verdict
A native integration between Zoom Phone and Salesforce exists and covers the core use case well: automatic call logging, click-to-dial, screen pops, and AI call summaries inside Salesforce Lightning. For most teams, the right choice depends on how much they need beyond what the native connector provides.
Sales teams that primarily need call activity tracked in Salesforce should activate the native Zoom for Lightning integration immediately. It is included with Zoom Phone plans, requires no third-party tool, and handles the most common call-to-CRM workflows out of the box.
Teams that need conditional workflows triggered by specific call events (missed calls creating follow-up tasks, long calls updating deal stages) should layer Zapier on top of the native integration to handle the event-driven logic the native connector does not cover.
Organizations with complex reporting requirements, custom Salesforce objects, or bidirectional sync needs should invest in a custom API integration using the Zoom Phone API and Salesforce REST API.
Before committing to a method, clarify what outcome you need from the integration.
If the goal is ensuring every call is logged against the right Salesforce record so activity reporting is accurate, the native integration handles it. If the goal is building call data into pipeline analytics, deal scoring, or custom workflows, a combination of the native connector and Zapier or custom development is the right path.
Either way, the quality of the contact data in Salesforce determines whether reps connect with the right people when they dial.
ZoomInfo, with its native integrations for both Salesforce and Zoom Phone and API and MCP access for any system, is the data enrichment layer that ensures reps are calling verified contacts at accurate numbers while the connector keeps every conversation tracked.
FAQ
Does Zoom Phone integrate natively with Salesforce?
Yes. Zoom offers a native Salesforce integration called "Zoom for Lightning," available through the Salesforce AppExchange. It embeds a Zoom Phone dialer widget inside Salesforce Lightning, provides click-to-dial from CRM records, logs call activity automatically, displays screen pops on inbound calls, and links Zoom AI call summaries to Salesforce records.
The integration is included with Zoom Phone plans at no additional cost, though AI call summary features require a qualifying Zoom Workplace paid plan.
What call data syncs between Zoom Phone and Salesforce?
The native integration syncs inbound and outbound call logs (including caller, callee, duration, and timestamp), call recordings, voicemail records, SMS activity, and AI-generated call summaries.
Call activity is logged as Tasks on matching Salesforce Lead, Contact, or Account records. Contact lookup on inbound calls matches the caller's number against Salesforce records to display the correct record before the rep answers.
Can I use Zoom Phone's click-to-dial from inside Salesforce?
Yes. Once the Zoom for Lightning app is installed and the dialer component is added to Salesforce Lightning page layouts, reps can click any phone number on a Lead, Contact, Account, or Opportunity record to initiate a Zoom Phone call directly. The call is placed through Zoom Phone and logged against the Salesforce record automatically.
Does the integration work with Salesforce Classic?
No. The native Zoom for Lightning integration requires Salesforce Lightning Experience. Organizations still running Salesforce Classic would need to either migrate to Lightning or use Zapier or a custom API integration to connect Zoom Phone call data to Salesforce.
What Zoom Phone plan do I need for the Salesforce integration?
The native Salesforce integration is available on all Zoom Phone calling plans, including the US and Canada Metered plan (approximately $10/user/month), the US and Canada Unlimited plan ($15/user/month), and the Global Select plan ($20/user/month). AI Companion features like post-call summaries require a qualifying Zoom Workplace paid plan with AI Companion enabled.
Are Zoom Phone's AI call summaries available in Salesforce?
Yes. When AI Companion for Zoom Phone is enabled, post-call summaries (including key discussion points, dates, names, and next steps) are generated automatically and linked to the corresponding Salesforce record through the native integration. This eliminates manual note-taking and gives managers a structured recap of every call inside the CRM.
How does ZoomInfo improve a Zoom Phone-Salesforce workflow?
ZoomInfo solves the data quality problem that no call-logging integration addresses. Before a rep dials, ZoomInfo ensures the Salesforce contact record has a verified direct-dial phone number (so the call connects), an accurate job title (so the conversation is relevant), and current employment details (so the rep is not calling someone who left).
ZoomInfo integrates natively with both Salesforce and Zoom Phone, and its Buyer Intent data can prioritize which accounts should receive call outreach based on active research signals. The result: more calls connect, activity logs against accurate records, and AI call summaries attach to contacts who are verified and reachable.
What happens to call logs if the integration disconnects?
Calls made during a disconnection are not retroactively logged in Salesforce. Call data remains in Zoom Phone's own call history and can be accessed through the Zoom admin portal, but the Salesforce activity records for those calls would need to be created manually or through a bulk sync after the integration is restored.
The native integration does not include a built-in mechanism for backfilling missed activity logs during an outage.
