Pipedrive Email Sync: Full Setup Guide

Setting up Pipedrive email sync means connecting Gmail, Outlook or any IMAP account so incoming and outgoing mail syncs automatically into deal and contact records, or, on plans and workflows where full sync isn’t the right fit, using Smart BCC to track individual threads by forwarding them to a unique address. The setup itself takes about five minutes. What actually determines whether it works well six months in is understanding the plan requirement, the attachment and delay limits, and — the part most setup guides skip — exactly when Pipedrive links an email to a deal on its own versus when a rep has to do it by hand.

This guide walks through both paths: full email sync for Gmail, Outlook and IMAP, and Smart BCC as the manual alternative, along with the 2025-2026 limitations worth planning around before you commit to one or the other.

What does Pipedrive email sync actually do?

Pipedrive email sync connects a real email account — Gmail, Office 365/Outlook, Microsoft Exchange, or any IMAP-compatible provider — so incoming and outgoing messages sync into Pipedrive’s Sales Inbox and attach automatically to the deal or contact record tied to the sender or recipient’s address, according to Pipedrive’s own email sync documentation. It’s a genuine two-way sync: replies sent from Gmail or Outlook appear in Pipedrive, and emails sent from inside Pipedrive land in the connected account’s sent folder, so a rep can work from either interface without losing thread continuity.

This is different from a basic CRM integration that just logs a copy of an email after the fact. Full sync means every message in a synced folder becomes visible and searchable inside Pipedrive, tracked opens and link clicks show against the record, and a manager can review an entire deal’s email history without asking the rep to forward anything. That visibility is also the tradeoff — full sync means granting Pipedrive read/write access to the connected mailbox, which is why some teams choose Smart BCC instead for accounts where broader access isn’t appropriate.

How do you set up email sync in Pipedrive for Gmail or Outlook?

Open your account menu in the top-right corner, go to Personal preferences > Email sync, and click + Email account. From there:

1. Choose your provider. Gmail/Google Workspace and Office 365/Outlook use OAuth — you’ll be redirected to sign in and grant permission directly, no password entry inside Pipedrive. Exchange (EWS) and generic IMAP accounts require entering server settings and credentials manually.
2. Set your sync history window. Pipedrive lets you choose how far back to sync, up to two years of existing email history. Syncing the full two years gives new reps context on every past conversation with a contact, but it also means a large initial sync — for a busy mailbox, picking a shorter window (30-90 days) speeds up the first sync and avoids importing years of unrelated mail.
3. Pick folders or labels to sync. You can sync every folder or scope it to specific ones — useful if a mailbox mixes sales conversations with unrelated internal threads you don’t want cluttering deal timelines.
4. Set a blocklist. Block specific addresses or entire domains from syncing, which matters for filtering out internal distribution lists, automated notifications, or anything that would otherwise attach noise to a contact record.
5. Click Start sync. The initial sync runs in the background; how long it takes depends on the history window and mailbox size.

Once connected, Pipedrive’s official setup article confirms all incoming and outgoing mail syncs automatically and links to the corresponding contact and deal records by matching email addresses. Test it by sending a message to an existing contact and checking that it appears on that contact’s Activities tab, then reply from Gmail or Outlook directly and confirm the reply shows up in Pipedrive within a few minutes — that round trip is the real test of two-way sync, not just the outbound half.

Email sync, calendar sync and contacts sync are three separate toggles

Pipedrive groups email, calendar and contacts syncing under the same provider connection, but they’re independent settings, not one bundled switch, according to Pipedrive’s provider-sync documentation. Connecting Gmail for email sync doesn’t automatically turn on calendar or contacts sync from that same account — each has its own toggle, and a common setup mistake is assuming turning on email sync handles meeting scheduling too, then discovering weeks later that calendar events booked outside Pipedrive never showed up on the activity timeline. If your rollout includes meeting scheduling or contact enrichment from the connected account, check those toggles explicitly during setup rather than assuming email sync covers them.

This also matters for the mobile app. Once an account is connected on desktop, the same synced mail is available through Pipedrive’s mobile app without a separate connection step, but push notifications for new synced email are a distinct setting from the sync itself — worth checking on a phone during setup rather than assuming a working desktop sync means a rep will get notified on mobile the moment a hot lead replies.

What happens to tracking and AI features once sync is live

Once an account is connected, every synced message gets open and click tracking by default — an eye icon on a message indicates it’s been opened, and a cursor icon shows a link inside it was clicked. Tracking can be turned off per individual message for anything that shouldn’t be tracked (an internal forward, for instance), which matters for teams operating under strict data-handling policies where blanket tracking on every email isn’t appropriate.

Users with account settings access also get AI-assisted email tools once sync is active: thread summarization for a long back-and-forth, AI-drafted replies, and suggested next messages based on the conversation so far. These sit on top of the sync connection rather than requiring separate setup, but they only work on synced mail — a thread tracked through Smart BCC gets the linking and visibility benefits of Smart BCC, not the same AI tooling that full sync’s continuous connection enables.

How long full setup actually takes, by path

The OAuth-based providers are fast; the manual ones and the per-message workflow are a different kind of time cost entirely:

That tradeoff is worth stating plainly when scoping which path fits a team: full sync is a one-time setup cost with effectively zero ongoing effort per email, while Smart BCC has no setup cost at all but adds a small manual step to every single message a rep wants tracked, forever. For a rep sending dozens of deal-relevant emails a day, that manual step adds up fast enough that full sync usually wins on pure time economics once a team is past the Lite plan.

Setting up a shared team inbox

A personal sync is private to the connecting user by default — nobody else sees it unless you change the sharing settings. For a shared address like sales@company.com or support@company.com, set up a team email account instead. Team accounts let an admin configure which team members can view and manage the synced mail, default visibility for new messages, how far back the sync starts, and which folders sync, all separate from any individual rep’s personal sync. This matters for handoffs: a shared inbox synced as a team account means any rep who picks up a deal can see the full conversation history, not just the messages that happened to route through their own connected mailbox.

Who can see synced email, and how do you keep private mail private?

Synced email is only visible to colleagues when it’s both linked to a Pipedrive item and marked Shared, which means the default visibility setting is the most important privacy decision in the whole rollout. Per Pipedrive’s email privacy documentation, a personal account can be set to Private, where conversations can still be linked to deals and contacts but only the account owner sees them, or Shared, where other users see a conversation only once it’s linked to an item they already have access to. Team accounts use a slightly different pair of options: Team only, visible to selected team members, or Shared, visible to everyone in the company.

Three details of that model matter in practice:

• Shared doesn’t mean the whole mailbox is exposed. An unlinked email stays in the owner’s Sales Inbox regardless of the sharing setting. Colleagues see a message only from the detail view of the deal or contact it’s linked to, and only if they have permission to view that item.
• Visibility can be overridden per message. A rep can flip an individual email to private or shared from the Sales Inbox or the linked item, and that choice overrides the account default. It gives reps a way to hold back one sensitive thread without disconnecting sync.
• Visibility inherits item permissions. If your visibility groups limit who can see a given deal, a shared email attached to that deal is only as visible as the deal is. Check the two settings together, not separately, before assuming a shared thread is company-wide.

Which default fits depends on the team. A sales team where every rep needs to pick up each other’s deals is usually best served by Shared as the default, since the whole point of syncing is that deal history survives a handoff. A team handling sensitive negotiations, or an executive whose mailbox mixes deal mail with other correspondence, is better off with Private as the default and a habit of sharing specific threads deliberately. Either way, decide this before the first sync runs, because an initial sync with a two-year history window will bring in a lot of mail and it’s much easier to set the default first than to audit thousands of messages afterward.

Departures are the case teams forget to plan for. When a rep leaves, their connected account is a personal credential tied to their mailbox, so someone needs to disconnect it, decide what happens to the synced history that’s linked to deals (the deal records themselves stay with the company), and reassign the open deals and their linked contacts. Building that into an offboarding checklist prevents a former employee’s mailbox from continuing to sync into records after their access should have ended, and it prevents the opposite problem, a manager discovering that a departing rep’s Private default meant no colleague can see the thread history on the deals they inherited.

Smart BCC: the manual alternative to full sync

Smart BCC exists for situations where full inbox access isn’t the right call, or where you just want specific threads tracked rather than an entire mailbox. Instead of connecting an account, you copy a unique address from Settings > Email sync > Smart BCC and paste it into the BCC field of any email you want captured. According to Pipedrive’s Smart BCC documentation, a copy of that message lands in your Pipedrive Mail tab and can be linked manually to the relevant deal, lead or contact.

Two requirements make or break Smart BCC, and both fail silently rather than throwing a visible error:

• SPF or DKIM must be correctly configured on the sending domain. If both authentication methods fail, the email simply doesn’t sync — no error message, no notification, it just never shows up. This is the single most common reason teams think Smart BCC is broken when it’s actually a domain configuration issue their IT team can fix in minutes once it’s flagged.
• Every reply needs the same BCC treatment. Smart BCC isn’t a persistent connection — if a customer replies and you forward that reply without BCC’ing the same address again, the thread breaks in Pipedrive even though the conversation continues normally in your inbox.

Other Smart BCC limits worth knowing before you rely on it: the maximum message size including attachments is 20MB, group-emailing tools generally strip BCC’d recipients so Smart BCC doesn’t work through them, and Pipedrive specifically advises against forwarding one email to multiple deal-specific BCC addresses at once — send it once, to the address for the deal it actually belongs to. Deal- and lead-specific BCC addresses exist precisely for that case: instead of the generic address plus manual linking, a BCC address tied to one specific deal links the message automatically on arrival.

When does Pipedrive link an email to a deal automatically?

This is the detail most setup guides skip, and it’s the one that causes the most confusion after go-live. Pipedrive links a synced or BCC’d email to a deal automatically only when the associated contact has exactly one open deal. If that contact has two or more open deals running at the same time, Pipedrive has no reliable signal for which one the email belongs to, so it doesn’t guess — the email lands in the Sales Inbox unlinked, and a rep has to open it and link it manually to the correct deal.

For a sales-first team where most contacts carry a single active deal, this is invisible in practice. For a team that regularly runs parallel deals with the same contact — a services company selling both a new engagement and a renewal to the same buyer, for instance — this is worth flagging in training, because an unlinked email sitting in the Sales Inbox looks like a sync failure when it’s actually working exactly as designed. Automatic linking itself is a setting under Personal preferences > Email sync > General settings, and if no contact exists at all for a given email address, Pipedrive creates a new person record automatically rather than leaving the message orphaned.

Current limitations to plan around (2026)

A few constraints are worth knowing before setup, not after a rep hits them mid-project:

• Plan requirement. Two-way email sync is a Growth-plan-and-higher feature under Pipedrive’s current four-tier structure (Lite, Growth, Premium, Ultimate); it isn’t available on Lite at any price. Growth runs $39/seat/month on annual billing, $49 billed monthly, per Pipedrive’s published pricing — a real budget line if you’re scoping a fresh Pipedrive rollout and assumed email sync was included at the entry tier.
• Sync delay. Expect roughly 5-10 minutes between sending a message and seeing it land in a deal’s timeline under full sync. That’s normal latency in the sync schedule, not a malfunction, but it can make a fast back-and-forth look briefly out of order if someone checks the timeline mid-conversation.
• Attachment ceilings. 25MB per email through Gmail sync, 20MB through Outlook sync, and 20MB total (message plus every attachment combined) through Smart BCC. A contract PDF bundled with a scanned signature page is exactly the kind of thread that can quietly exceed these.
• Sending rate limit. Pipedrive caps outbound email at 40 actions per minute per company account, on top of whatever limit Gmail or Outlook separately enforces. A rep sending a genuinely large batch of follow-ups through Pipedrive’s inbox can hit this and have sends fail partway through with no obvious explanation unless they know the ceiling exists.
• Unsupported characters in addresses. Recipient addresses containing characters like backslash, forward slash, quotation marks, angle brackets, pipe, asterisk or the caret symbol can silently prevent delivery — rare, but worth checking first if one specific address in an otherwise-working sync keeps failing.
• Credential and settings changes break authentication. If a domain’s email server settings or account credentials change while sync is active, authentication fails and the connection needs re-authenticating through Personal preferences, not just retried.

Troubleshooting a sync that stops working

Most email sync failures trace back to one of a small set of causes, according to Pipedrive’s troubleshooting documentation. Work through them in this order rather than jumping straight to disconnecting and reconnecting:

First, check whether credentials or server settings changed recently — a password reset, an IT-driven domain migration, or a security policy change on the mailbox provider side will break the authenticated connection even though nothing changed inside Pipedrive itself. Re-authenticate from Personal preferences > Email sync before doing anything more drastic. Second, check active filters in the source inbox — a Gmail filter or Outlook rule that archives, labels, or redirects certain mail before Pipedrive’s sync process sees it will make messages appear to vanish. Third, confirm the message actually reached a synced folder; label and folder scoping set during initial setup means anything outside that scope was never going to sync in the first place, which looks identical to a broken sync from the rep’s point of view. If none of that resolves it, reconnecting via “Add another account” rather than a straight reconnect avoids some of the state issues that come with re-establishing the same connection in place.

Choosing between full sync and Smart BCC

The decision usually comes down to how much of the mailbox genuinely belongs in Pipedrive and who else needs visibility into it. Full sync is the right call for a dedicated sales mailbox where every message is deal-relevant and the team wants zero manual effort keeping records current — most SMB sales teams running Pipedrive as their core CRM land here once they’re past initial rollout. Smart BCC fits better for a personal or mixed-use inbox where only specific threads are deal-relevant, for compliance situations where granting full mailbox access isn’t appropriate, or as a stopgap on a Lite plan before a Growth upgrade is budgeted. Some teams run both: full sync on a dedicated sales address, Smart BCC for executives or account managers whose inbox mixes sales and non-sales correspondence and who don’t want the whole thing visible in Pipedrive.

This same setup discipline — get the sync mechanics right before layering automation on top — applies just as much outside Pipedrive. Agencies doing broader CRM setup work for clients run into the identical sequencing problem on other platforms: get the core connections and data flow right first, automation second. HighLevelAutomationTeam’s guide to running GoHighLevel setup as an agency service and Autoesta’s version of that same playbook both make the same point from the GoHighLevel side: rushing straight to automation before the underlying connections are solid is the most common reason a CRM setup project needs rework later.

What to check before you call setup done

A synced mailbox that shows a green checkmark isn’t the same as a setup that will hold up under real use. Before calling it finished, confirm: the two-way round trip actually works (send from Pipedrive, reply from Gmail/Outlook, confirm both directions land); the blocklist excludes internal noise like automated notifications and distribution lists; team members on a shared inbox have the correct visibility settings, not defaulted to more or less access than intended; and at least one contact with multiple open deals has been tested specifically, so the team sees a manually-linked email in the Sales Inbox before it happens for the first time on a live deal rather than looking like a bug during a real sales cycle. None of this is complicated individually — it’s the kind of checklist that’s easy to skip under project time pressure and expensive to discover gaps in three months later, which is exactly the sequencing problem a proper Pipedrive implementation is meant to prevent. If Workflow Automation is next on the list once sync is stable, Pipedrive Automation: What to Automate First covers what to build once emails are reliably landing on the right records.

Getting email sync wrong doesn’t usually show up immediately — it shows up three weeks later as a manager asking why a deal’s email history looks incomplete, or a rep insisting they replied to a lead that Pipedrive shows no record of. Fifteen minutes spent testing the two-way round trip and the multi-deal linking behavior during setup is cheaper than diagnosing that gap after a deal has already gone quiet.