Pipedrive email sync brings sales correspondence into your CRM so you can send, receive and reply from its Sales Inbox. Our recommendation is to connect one mailbox first, check who can read its messages and confirm which deal each conversation belongs to before switching on follow-ups. Pipedrive currently offers email sync on Growth and higher plans, according to its email-sync documentation.
Table of Contents
Which plan supports Pipedrive email sync?
The current account limits distinguish a single personal mailbox from a setup with several connections:
| Plan | Connected accounts | Account types |
|---|---|---|
| Growth | 1 | Personal |
| Premium | 3 | Personal or team |
| Ultimate | 5 | Personal or team |
For an individual salesperson with one address, Growth is the starting point to evaluate. A shared sales address or several connected mailboxes changes the requirement. Confirm your actual subscription before making changes; these are current plan names. If you are still choosing a CRM, start with our HubSpot versus Pipedrive comparison.
Check your provider and sender address
Pipedrive lists Gmail/Google Apps, Office 365/Outlook, Exchange through EWS and IMAP-compatible accounts among its supported providers. Select the service that actually hosts your mailbox. A company domain alone does not identify the provider.
If you need to send under an alias, check that separately. Pipedrive’s personal-account settings support verified Gmail aliases; that option does not extend to Outlook, Exchange or other IMAP accounts. Write down the intended sender and reply address before connecting anything.
Connect a mailbox with a controlled history
Use Pipedrive’s setup instructions and work through these choices:
- Open the connection screen. From the account menu, open Personal preferences, then Email sync. Enter the address and begin setup.
- Authenticate with the provider. Select the correct service, sign in and review the access request.
- Choose personal or team use. Team Inbox requires Premium or above. For a team account, select the people who will manage its messages.
- Set the scope before starting. Choose the visibility, history start point and folders to include, then start syncing.
For a pilot, choose a recent period and a relevant sales folder. Avoid importing years of unrelated correspondence merely because the option exists. Changing the history start date later does not remove messages already imported, as the account settings guide explains. Review the archiving and deletion settings before treating CRM cleanup as harmless tidying.
Separate inbox access from record visibility
A personal Sales Inbox remains private. A conversation marked shared can be read by colleagues through linked records only when the relevant record permissions also allow access. Team accounts instead offer team-only or shared visibility. Giving someone access to an organisation alone may be insufficient if they cannot access its linked items. These distinctions are set out in Pipedrive’s email visibility rules.
Changing the default applies to subsequently synced or forwarded emails; it does not rewrite every existing conversation’s setting. Only the conversation owner can change its email visibility. Someone who can read a linked message may still be unable to reply from that view when the conversation belongs to another user.
Agree which business messages should be shared, then check the result with an ordinary colleague account. Include a private test thread as well as a shared one.
Check the conversation’s deal link
Automatic linking uses contact relationships, but Pipedrive cannot choose the correct opportunity when a person has multiple open deals, leads or projects. Won, lost or deleted deals do not qualify for automatic linking, and earlier emails are not linked retroactively when you create a new item. You can link the conversation manually from the inbox or record. See the conversation-linking guide.
Linking applies to the whole conversation, not one message within it. A threaded conversation can link to only one deal, lead or project. Give separate opportunities distinct email subjects and review the linked record before sharing a thread containing several proposals.
Test one real working pattern before automating
Illustrative example: a two-person consultancy handles a website proposal and a maintenance renewal for the same customer. The owner connects their work mailbox and uses clearly separate conversations for each job. The colleague needs enough history to cover an absence, without reading unrelated negotiations.
Use a harmless sample enquiry to rehearse the handover. Confirm the sender address, locate the incoming reply, check the intended opportunity and ask the colleague to find the next action. Repeat with a conversation they should not see. Write down who answers when the owner is away; a visible email is not itself an assignment.
If several people primarily need to work one shared address, compare that workflow with our shared inbox software guide before expanding the CRM setup.
Add automated follow-ups only after the sender works
Email automations require Growth or higher and a working email connection. Dynamic sender options based on the item owner or triggering user require that person’s connected personal account to be their default; otherwise sending fails. A reply action within an existing conversation needs an earlier email step, with the in-thread option linked to that step.
Pipedrive distinguishes a timed delay from waiting for an event. Each event-wait step can run for up to seven days; unmet conditions stop it. Test both reply and no-reply paths with controlled addresses before relying on a follow-up sequence.
Diagnose the missing message before reconnecting
Follow the symptom rather than assuming every missing email means a broken connection:
| Symptom | First check |
|---|---|
| Connection authentication fails | Check changed credentials or server settings and re-authenticate. |
| Message absent from Sales Inbox | Check inbox filters and the folders or labels selected for syncing. |
| Message exists but not on a deal | Inspect its linked record. |
| Sending fails | Check the provider’s sending restrictions and the exact error. |
Pipedrive’s troubleshooting guide covers the connection, filters and linking checks. Its sending guidance also notes that provider limits still apply. If the fault persists, record the affected account, message time and error for support. Expand the rollout only when sending, replies, linking and colleague access work as intended.
Sources reviewed 15 September 2026. This guide is based on current Pipedrive documentation; the consultancy example is illustrative.
