Salesforce Gmail Integration: The Complete Guide for 2026
- Buyer's Guide, CRM
- 20 min
- September 1, 2026
Salesforce and Gmail are two of the most important systems in a modern sales stack. But connecting them isn’t as straightforward as it sounds.
Customer conversations happen in Gmail. Meetings happen in Google Calendar. New stakeholders enter email threads. Follow-ups get sent. Important buying signals appear in conversations.
But your revenue team still needs that activity in Salesforce. That is what a Salesforce Gmail integration is designed to solve.
In 2026, however, “Salesforce Gmail integration” can mean several different things. Salesforce itself offers Gmail integration, Einstein Activity Capture, Salesforce Inbox, and related synchronization capabilities. Third-party platforms can add another layer of activity capture, automation, matching, and intelligence.
So the question is no longer simply: How do I connect Gmail to Salesforce?
It’s: How much of the customer activity happening in Gmail do you need Salesforce to understand, and what do you need Salesforce to do with it?
This guide explains what the Salesforce Gmail integration does today, how to set it up, where the native option works well, where teams can run into limitations at scale, and when a dedicated Salesforce activity-capture or revenue-data platform makes sense.
Get our latest insights into your inbox
What is Salesforce Gmail integration?
A Salesforce Gmail integration, sometimes referred to as a Salesforce connector for Gmail, connects a user’s Gmail account with Salesforce so they can access Salesforce information from Gmail and associate email activity with Salesforce records.
Salesforce’s native Gmail Integration allows users to see, create, and modify Salesforce records from Gmail. With Enhanced Email enabled, users can relate emails to Salesforce records while composing messages and associate emails with contacts, leads, accounts, opportunities, cases, and supported records.
The experience has also evolved. Salesforce made Gmail Integration available inside Sales Cloud Everywhere, bringing the Gmail functionality into its Chrome side panel alongside other Salesforce capabilities.
Separately, Einstein Activity Capture (EAC) can automatically capture email and calendar activity from connected Google accounts and associate that activity with Salesforce records.
Since Summer ’25, Salesforce has introduced Sync Email as Salesforce Activity, which allows captured emails to be stored as Salesforce activity data, including Task and EmailMessage records. This makes the email data available to standard Salesforce reports, workflows, triggers, APIs, and other platform capabilities.
So there are really two related layers:
- Gmail integration: Work with Salesforce from inside Gmail.
- Activity capture: Automatically bring customer email and calendar activity into Salesforce.
For many teams, you will want both.
Salesforce Gmail Integration is also part of a broader ecosystem of Chrome extensions built to make Salesforce easier to use from the browser. If you’re evaluating those tools alongside Gmail integration,
What can you do with Salesforce Gmail integration?
The native integration covers the core workflows most sales teams expect.
1. View Salesforce records from Gmail
Sales reps can open an email in Gmail and access relevant Salesforce information without constantly switching between applications.
Depending on configuration, they can view and work with Salesforce records associated with the people they’re communicating with.
This is particularly useful for basic CRM lookups:
- Is this person already a contact?
- Which account are they associated with?
- Is there an open opportunity?
- What activity has already been recorded?
- Do I need to create a Salesforce record?
Salesforce describes the Gmail integration as a way for users to see, create, and modify Salesforce records directly from Gmail.
2. Log emails to Salesforce
Users can associate emails with relevant Salesforce records from Gmail.
Enhanced Email is important here. Salesforce requires Enhanced Email for relating Gmail emails to Salesforce and stores email messages as richer email records rather than treating everything as a simple task.
This gives sales teams a much better record of customer conversations.
3. Automatically capture emails
Manual logging is not the only option.
With Einstein Activity Capture and Sync Email as Salesforce Activity enabled, Salesforce can automatically sync emails sent and received through connected Google accounts into Salesforce.
That changes the workflow from:
Rep sends email → remembers to log it
to:
Rep sends email → Salesforce captures the activity
For organizations trying to improve CRM completeness, this is one of the biggest benefits of connecting Gmail and Salesforce.
4. Sync Google Calendar activity
Salesforce can also capture and synchronize calendar activity through Einstein Activity Capture.
That gives Salesforce visibility into meetings alongside email activity.
Salesforce can match Google Calendar events with relevant Salesforce users, contacts, and leads. It can also sync attendee information, subject to Salesforce’s matching and attendee limits.
5. Create Salesforce records from Gmail
The Gmail integration can also reduce the friction involved in creating CRM records.
If someone new enters a sales conversation, the rep can create or update the relevant Salesforce record without leaving Gmail.
This is important because the best CRM workflow is often the one that requires the fewest context switches.
How to set up Salesforce Gmail integration
The exact setup depends on whether you’re using the basic Gmail integration, Einstein Activity Capture, Salesforce Inbox, or a combination.
For the native Gmail integration, Salesforce’s current setup process starts in Salesforce Setup.
Step 1: Enable Enhanced Email
Before enabling Gmail Integration, Salesforce recommends verifying that Enhanced Email is enabled.
Enhanced Email is required to relate Gmail emails to Salesforce records.
Step 2: Enable Gmail Integration
In Salesforce:
Setup → Quick Find → Gmail Integration and Sync
Enable the setting that allows users to access Salesforce records from Gmail.
Salesforce’s current documentation specifically instructs administrators to enable Gmail Integration and Sync and then enable Enhanced Email with Gmail.
Step 3: Configure Einstein Activity Capture
If your objective is automatic activity capture rather than simply accessing Salesforce from Gmail, configure Einstein Activity Capture.
This is where administrators define how email, events, and other activity should be captured and synchronized.
With the newer Sync Email as Salesforce Activity architecture, captured email can become standard Salesforce activity data.
Step 4: Configure users and permissions
Users need the appropriate Salesforce permissions and must connect their Google account.
The Gmail integration itself is accessed through Salesforce’s Gmail experience/Chrome side panel, while Sales Cloud Everywhere also provides broader Salesforce functionality within Chrome.
Step 5: Test email matching
Don’t stop after confirming that an email appears in Salesforce.
Test whether emails are being associated with the right:
- Contact
- Lead
- Account
- Opportunity
- Other relevant records
This becomes increasingly important as your CRM becomes more complex.
What Salesforce Gmail integration does well
The native option is genuinely useful—and teams should evaluate it before buying another tool.
- It is native to Salesforce: There is no question about whether Salesforce understands its own data model.
The integration is designed around Salesforce records, permissions, activity timelines, and the Salesforce platform.
- It reduces manual CRM work: A rep can work from Gmail while still interacting with Salesforce.
And with Einstein Activity Capture, much of the activity logging can happen automatically.
- It supports standard sales workflows: For organizations primarily concerned with:
- Contacts
- Leads
- Accounts
- Opportunities
- Email activity
- Calendar activity
The native Salesforce stack can cover a significant portion of the requirement.
- Email data is becoming more usable inside Salesforce: This is an important 2026 change.
With Sync Email as Salesforce Activity, captured email can be stored as Salesforce activity data and used by reports, workflows, triggers, APIs, and AI-related capabilities.
Salesforce is also rolling organizations onto this architecture during 2026, with migration timing varying by org.
So if you’re reading an older article claiming that EAC email data necessarily lives outside Salesforce’s standard data model, check the publication date.
That is no longer a complete description of the product.
Where the native Salesforce Gmail integration starts to break
The native integration is strong for the basic use case. The harder question is what happens when your revenue process becomes more complicated.
This is where the distinction between connecting Gmail and capturing revenue activity comprehensively becomes important.
1. Email aliases can create problems
Einstein Activity Capture requires the connected email account to be the user’s primary account.
Salesforce explicitly states that EAC does not support email aliases. When a connected account has an alias, unexpected behavior can occur around sending and email threading.
This matters for organizations where people regularly send from addresses such as:
- sales@company.com
- partnerships@company.com
- support@company.com
- regional aliases
- acquired-company domains
- brand-specific aliases
A basic one-user/one-primary-mailbox environment is considerably simpler than a multi-address revenue organization.
2. Shared mailboxes are more complicated
Shared inboxes are another area where standard user-to-mailbox assumptions become difficult.
Salesforce’s synchronization architecture relies heavily on mapping a Salesforce user to an external mailbox. Salesforce documents cases where duplicate email addresses prevent a unique connection. For example, when a shared mailbox address is assigned to multiple Salesforce users.
This is a structural issue, not simply a setup checkbox.
If multiple people operate from the same mailbox, you need to think about:
- Who owns the activity?
- Which Salesforce user should receive it?
- Which account or opportunity should it belong to?
- Should every participant see it?
- How do you avoid duplicate activity?
- How do you preserve the history when ownership changes?
That is where basic mailbox synchronization starts becoming a revenue-data problem.
3. Custom objects require more thought
This area is more nuanced in 2026 than older Salesforce content suggests.
Historically, native activity capture had significant limitations around custom objects.
Today, Salesforce’s Sync Email as Salesforce Activity architecture provides Flow-based matching capabilities. Salesforce specifically provides an Activities: Match Email to Records Flow action that can be customized to match email against additional records and business logic.
That is a meaningful improvement. But there is an important distinction: Possible does not mean automatic.
If your business depends on associating emails with custom objects, you may need to design and maintain custom matching logic rather than simply turning on Gmail integration.
And Salesforce’s own documentation still identifies custom-object scenarios as an area requiring configuration rather than assuming native automatic association.
For organizations with complex CRM architectures, this can become an administrative and Flow-maintenance exercise.
4. Multi-attendee meetings aren't as simple as they look
Meetings are one of the biggest tests of any Salesforce Gmail integration.
A one-to-one meeting is easy:
Rep ↔ Prospect
But enterprise buying processes look more like:
Rep + AE + SE + CFO + VP Sales + Procurement + IT + Legal
Salesforce can sync event attendees, but there are limits and matching rules.
Einstein Activity Capture supports up to 50 attendees per event, and attendees that don’t match Salesforce records don’t sync as Salesforce attendees.
There is another important limitation.
When Shared Activities is off, EAC can relate only one Salesforce contact or lead to an event. When Shared Activities is on, it can relate up to 50 matching contacts or one matching lead.
That means capturing a meeting is not necessarily the same thing as understanding the people involved in the buying process.
For teams operating with buying groups, this distinction matters enormously.
5. Historical data needs careful planning
With Sync Email as Salesforce Activity, Salesforce documents a limit of up to 50,000 historical emails per user from the previous 180 days.
There are also separate rules around migration, email insights, and historical data.
For example, organizations moving to Sync Email as Salesforce Activity can have different historical availability depending on whether they are setting it up or migrating an existing EAC implementation. Salesforce says existing customers can contact Support for Sync Email as Salesforce Activity with up to six months of historic emails.
So if you’re migrating from another activity-capture system or trying to reconstruct years of customer history, you should treat historical backfill as a separate requirement, not assume it comes automatically with the Gmail connection.
6. Automatic capture doesn't automatically mean correct capture
This may be the most important limitation of all.
Capturing activity is only half the problem.
You also need to answer:
Where does the activity belong?
Salesforce’s native matching uses email addresses and CRM relationships. With Sync Email as Salesforce Activity, Salesforce can customize matching through Flow, including more sophisticated matching logic.
But complex organizations frequently have:
- Duplicate contacts
- Multiple contacts sharing an email address
- Multiple opportunities at the same account
- Partner-led deals
- Multiple business units
- Parent/child accounts
- Acquired domains
- Shared mailboxes
- Aliases
- Contacts who participate in several buying processes
The more complicated the CRM, the more important matching becomes.
A Salesforce Gmail integration that captures 95% of your emails isn’t necessarily successful if a meaningful portion of those emails are attached to the wrong records, or nowhere useful at all.
7. Email storage becomes a Salesforce consideration
With Sync Email as Salesforce Activity, captured emails are stored as Salesforce activity data.
That is powerful because the data becomes available to Salesforce platform capabilities.
It also means the data counts toward your Salesforce storage allocation. Salesforce explicitly recommends managing and archiving older activity data as part of storage management.
For organizations with large email volumes, this changes the economics and architecture of the solution.
You’re no longer asking only:
“Can Salesforce capture our emails?”
You’re also asking:
“How much activity do we want to store in Salesforce, for how long, and what do we want to do with it?”
8. Attachments aren't automatically stored in Salesforce
Another easy detail to miss: Salesforce says email attachments aren’t synced or stored in Salesforce through Sync Email as Salesforce Activity.
Users need to access the attachment from the connected inbox.
For organizations where attachments themselves are important sales or account intelligence, that’s worth considering during evaluation.
The Bigger Problem: CRM activity vs. revenue intelligence
This is where the Salesforce Gmail integration category starts to evolve.
A basic integration answers:
Did an email happen?
A stronger activity-capture system answers:
What happened, who was involved, where should it be recorded, and what does it tell us about the customer relationship?
And a revenue intelligence layer goes further:
What does all of this activity tell us about pipeline, account engagement, buying groups, deal health, and what should happen next?
These are different jobs.
What should you look for in a Salesforce Gmail integration?
Before choosing a solution, evaluate it against your actual operating model.
Basic Requirements
If you’re a smaller team, you may only need:
- Gmail + Salesforce connection
- Email logging
- Calendar sync
- Contact lookup
- Opportunity lookup
- Basic record creation
- Salesforce activity timelines
The native Salesforce integration may be sufficient.
Scaling Requirements
If your organization is larger, start asking:
Activity capture
- Can it automatically capture emails?
- Can it capture meetings?
- Can it capture historical activity?
- Can it distinguish internal and external activity?
Matching
- How does it decide where an email belongs?
- Can it match to opportunities?
- Can it handle duplicate contacts?
- Can matching rules be customized?
- Can it support custom objects?
People and relationships
- Can it capture multiple meeting attendees?
- Can it identify new stakeholders?
- Can it update contact information?
- Can it understand relationships across an account?
Mailbox complexity
- Does it support aliases?
- Shared mailboxes?
- Multiple domains?
- Acquired companies?
- Different sender addresses?
Data architecture
- Where is the activity stored?
- Is it standard Salesforce data?
- Does it count toward Salesforce storage?
- Can Salesforce automation access it?
- Can it be queried through APIs?
Governance
- Can admins control what gets captured?
- Can confidential or irrelevant activity be excluded?
- Can activity visibility follow Salesforce permissions?
- Can the system prevent duplicate logging?
Native Salesforce Gmail integration vs. third-party platforms
The right answer isn’t automatically “buy a third-party tool.”
A better decision framework is:
|
Requirement
|
Native Salesforce
|
Dedicated activity / Revenue platform
|
|---|---|---|
|
Gmail connection
|
|
|
|
Salesforce context inside Gmail
|
|
Often
|
|
Basic email logging
|
|
|
|
Automatic activity capture
|
with EAC
|
|
|
Calendar capture
|
|
|
|
Standard Salesforce records
|
|
|
|
Advanced matching
|
Configurable
|
Often more extensive
|
|
Complex mailbox environments
|
Can require workarounds / configuration
|
Often stronger
|
|
Historical backfill
|
Subject to Salesforce limits/configuration
|
Depends on platform
|
|
Custom business logic
|
Flow/customization
|
Often purpose-built
|
|
Cross-system activity
|
Primarily Salesforce + Google ecosystem
|
Often broader
|
|
Relationship/buyer intelligence
|
Limited to configured Salesforce capabilities
|
Often a core capability
|
|
Revenue workflow intelligence
|
Requires additional Salesforce capabilities
|
Often built in
|
The important point is that these categories don’t necessarily replace one another.
A third-party platform may sit on top of Salesforce rather than replace Salesforce’s native Gmail functionality.
When should you consider a third-party Salesforce Gmail integration?
A dedicated platform becomes more interesting when your problem is no longer simply “connect Gmail to Salesforce.”
Consider one if:
- Your reps work across multiple inboxes or addresses: Aliases, shared mailboxes, multiple domains, and complex ownership models can make basic synchronization harder to manage.
- You need deeper historical data: If understanding a deal requires months or years of customer interactions, historical backfill becomes a first-class requirement.
- You have complex CRM matching requirements: If emails need to be associated with opportunities, accounts, custom records, partners, or other business entities, evaluate how much configuration the native Salesforce stack requires.
- Meetings are central to your sales proces: If your business depends on understanding every stakeholder involved in an enterprise deal, simply recording the existence of a meeting isn’t enough.
- CRM completeness is a business metric: If leadership wants reliable answers to questions such as:
- Who has engaged with this account?
- Which stakeholders are active?
- How many buying-group members have we identified?
- Is engagement increasing or declining?
- Which opportunities have weak coverage?
- Which accounts are going dark?
then you’re moving beyond email logging.
You’re building a customer activity data layer.
Where Nektar fits
There is a growing category of platforms focused specifically on turning customer-facing activity into usable revenue data.
Nektar is one example.
Rather than positioning these products simply as another way to put Gmail inside Salesforce, the more useful distinction is what happens after the activity is captured.
Nektar connects to systems including Google Workspace, Microsoft 365, Salesforce, and other revenue tools, builds a representation of activities, people, companies, opportunities, and their relationships, and writes relevant intelligence back into Salesforce.
That makes the category relevant when the requirement is broader than:
“Log my Gmail activity.”
and becomes:
“Give Salesforce a reliable picture of the customer activity and relationships happening outside the CRM.”
For teams evaluating this category, Nektar is one option to consider alongside other dedicated activity-capture and revenue-intelligence platforms.
The right choice depends on the complexity of your Salesforce architecture, mailbox environment, activity volume, matching requirements, governance model, and what you ultimately want to do with the data.
Salesforce Gmail integration: The 2026 Takeaway for Your Team
Salesforce’s native Gmail integration is much more capable than it was several years ago.
For many teams, it is a perfectly reasonable starting point.
You can work with Salesforce from Gmail, relate emails to CRM records, synchronize calendar activity, and through Einstein Activity Capture and Sync Email as Salesforce Activity, you can bring captured email into Salesforce’s standard activity architecture.
But “Gmail connected to Salesforce” doesn’t automatically mean “Salesforce has a complete picture of customer engagement.”
As your organization grows, the harder problems tend to be:
- Shared mailboxes
- Email aliases
- Multiple domains
- Custom CRM objects
- Complex matching
- Multi-attendee meetings
- Historical activity
- Duplicate records
- Activity ownership
- Data storage
- Cross-account relationships
- Buying-group visibility
That’s the point at which you should evaluate whether Salesforce’s native capabilities are enough, or whether a dedicated activity-capture or revenue-data platform makes more sense.
The best Salesforce Gmail integration isn’t necessarily the one with the longest feature list.
It’s the one that gets the right customer activity into the right Salesforce context, with enough accuracy and completeness for your revenue team to trust what it sees.
Frequently Asked Questions
Q: Is there a Salesforce Gmail plugin?
Yes. Salesforce provides a native Gmail integration that allows users to access Salesforce records and work with Salesforce data from Gmail. The Gmail functionality is also available through Salesforce's Sales Cloud Everywhere Chrome side panel.
The term “Salesforce Gmail plugin” is commonly used to describe this experience, although Salesforce's current product architecture includes more than a single plugin: Gmail Integration, Sales Cloud Everywhere, Einstein Activity Capture, and Salesforce Inbox address different parts of the workflow.
The term “Salesforce Gmail plugin” is commonly used to describe this experience, although Salesforce's current product architecture includes more than a single plugin: Gmail Integration, Sales Cloud Everywhere, Einstein Activity Capture, and Salesforce Inbox address different parts of the workflow.
Q: What is a Salesforce connector for Gmail?
A Salesforce connector for Gmail is a tool that connects Gmail with Salesforce so users can access CRM information, log or automatically capture email activity, and associate conversations with Salesforce records. Salesforce provides a native Gmail integration, while third-party platforms can offer additional activity capture, matching, automation, and revenue intelligence capabilities.
Q: Is Salesforce Gmail integration free?
There isn't a simple universal “Gmail integration price” because Salesforce's capabilities are tied to the Salesforce products, editions, licenses, and add-ons your organization uses.
The basic Gmail Integration is available across several Salesforce editions, while capabilities such as Einstein Activity Capture and Salesforce Inbox have their own availability and licensing considerations.
The basic Gmail Integration is available across several Salesforce editions, while capabilities such as Einstein Activity Capture and Salesforce Inbox have their own availability and licensing considerations.
Q: Does Salesforce automatically log Gmail emails?
It can.
Einstein Activity Capture can automatically capture Gmail email activity. With Sync Email as Salesforce Activity enabled, those emails can be stored as Salesforce activity records.
However, automatic capture does not mean every email will necessarily be captured, matched, and associated with every Salesforce record you want. Salesforce has specific filtering, matching, storage, historical-sync, and mailbox considerations.
However, automatic capture does not mean every email will necessarily be captured, matched, and associated with every Salesforce record you want. Salesforce has specific filtering, matching, storage, historical-sync, and mailbox considerations.
Q: Can Salesforce Gmail integration sync Google Calendar?
Yes. Salesforce's activity-sync capabilities can synchronize Google Calendar events and attendees with Salesforce, subject to the applicable Einstein Activity Capture configuration and matching rules.
Q: Does Salesforce Gmail integration support email aliases?
Einstein Activity Capture does not support alias email addresses as the connected account. Salesforce explicitly recommends using the user's primary Google or Microsoft email address.
Q: Can Salesforce Gmail integration handle shared mailboxes?
Shared mailbox scenarios require careful evaluation. Salesforce's synchronization architecture relies on user-to-mailbox relationships, and Salesforce documents errors when the same email address is assigned to multiple Salesforce users.
Q: Can Salesforce Gmail integration capture old emails?
Yes, but within defined limits.
With Sync Email as Salesforce Activity, Salesforce documents synchronization of up to 50,000 historical emails per user from the previous 180 days. Migration scenarios can have different historical options.
With Sync Email as Salesforce Activity, Salesforce documents synchronization of up to 50,000 historical emails per user from the previous 180 days. Migration scenarios can have different historical options.
Q: Can Salesforce Gmail integration work with custom objects?
The answer in 2026 is with configuration, not simply out of the box.
Salesforce's newer Sync Email as Salesforce Activity architecture provides Flow actions for custom matching and association logic. This can extend how captured emails are matched to Salesforce data, but organizations with complex custom-object requirements should validate the exa
Salesforce's newer Sync Email as Salesforce Activity architecture provides Flow actions for custom matching and association logic. This can extend how captured emails are matched to Salesforce data, but organizations with complex custom-object requirements should validate the exa
Q: How many meeting attendees can Salesforce sync?
Einstein Activity Capture supports up to 50 attendees per event. Attendees must also meet Salesforce's matching requirements to become corresponding Salesforce records.
Q: Is a Salesforce Gmail integration the same as an activity-capture platform?
No.
A Gmail integration primarily connects Gmail and Salesforce and lets users work with Salesforce from their inbox.
An activity-capture platform focuses on automatically collecting customer-facing activity and getting it into the correct CRM context. Some products, including Salesforce itself, combine both capabilities.
A Gmail integration primarily connects Gmail and Salesforce and lets users work with Salesforce from their inbox.
An activity-capture platform focuses on automatically collecting customer-facing activity and getting it into the correct CRM context. Some products, including Salesforce itself, combine both capabilities.
Enjoyed our content? Follow Nektar on LinkedIn
