The Pipedrive Gmail Add-On: What the Side Panel Does, and Where Gmail's Limits Start
What the Pipedrive Gmail side panel shows and creates, how it differs from email sync, and the published Google sending limits that decide what Gmail cannot be.
The Pipedrive Gmail add-on shows CRM context beside an open email and lets a rep create people, deals, activities and notes without leaving the inbox. It is a side panel rather than a sync mechanism, and it does not change Google's published sending limits.
Key takeaways
- With no email open the panel shows today's activities; with one open it shows the sender's details, deals, activities and notes.
- The add-on is not email sync: correspondence reaches Pipedrive through email sync or Smart Bcc, which the add-on does not replace.
- Google publishes a daily sending limit of 2,000 messages per user account, with 3,000 external recipients and 2,000 unique external recipients per day.
- Sending limits apply over a rolling 24-hour period rather than resetting at a set time of day.
Reviewed and updated August 15, 2026
The Pipedrive Gmail Add-On: What the Side Panel Does, and Where Gmail's Limits Start
The Pipedrive Gmail add-on solves a small problem very well. A rep reading an email should be able to see the deals, activities and notes attached to the sender without opening another tab, and should be able to create the follow-up from where they are standing. That is the whole product, and it is worth installing.
The trouble starts when the same add-on gets read as evidence that Gmail can be the sending engine for an outbound programme. It cannot, and the reason has nothing to do with Pipedrive. Google publishes the numbers, and they are lower than most plans assume.
Installing it, and the one error everybody hits
Installation runs through Gmail's add-on menu or the Google Workspace Marketplace: search for Pipedrive CRM and install. Pipedrive's knowledge base article on the add-on walks the authorisation step, after which the add-on appears in the Gmail sidebar and you click Log in to connect the Pipedrive account.
One failure is common enough that Pipedrive documents it explicitly. If installation or authorisation produces "Sorry, unable to open the file at this time", the cause is typically several Google accounts signed into the same browser window, with Google attempting to authorise using the wrong session. Pipedrive names three fixes: use an incognito window and sign in only with the intended account, sign out of every Google account and back into just the one, or create a dedicated Chrome profile for the work account. That third option is the one that stops it recurring, and it is a good idea for anyone who runs a personal and a work Google account in the same browser for any reason.
What the side panel actually shows
The add-on behaves differently depending on whether an email is open, which is a small design decision that turns out to matter for how people use it.
With no email open, the panel shows an overview of the activities scheduled for today. That makes it a lightweight day view living inside the inbox, which is where a rep already is.
With an email open, the panel checks whether the sender exists in Pipedrive. If the address is not linked to a person, you get an Add new person option, and Pipedrive documents that the person is added and linked to the email address immediately, ready for deals, activities and notes. If the address is already linked, the panel shows the person's details, their deals, their activities and their notes, all viewable and editable without leaving Gmail. Editing covers name, email, phone and organization, saved with an update button.
Three creation actions sit alongside the view. Add deal creates a deal for the contact, with a link through to open it in Pipedrive proper. Add activity creates an activity and lets you mark it done from a toggle in the panel. Add note attaches a note to a person or a deal, and Pipedrive states the note is synced instantly.
The scheduler is the one part of the add-on that is tier-gated. Pipedrive notes that the meeting scheduler is available on Growth and higher plans. Where it is available, composing an email and clicking the Pipedrive logo in the toolbar opens a window for selecting available time slots, inserts an availability link into the message, and lets the recipient pick a time. Availability itself is managed from the same window.
- An overview of activities scheduled for today
- Nothing sender-specific, because there is no sender
- Add new person option
- Person is created and linked to the address immediately
- Deals, activities and notes become available straight after
- Person details, deals, activities and notes
- Inline editing of name, email, phone and organization
- Add deal, add activity and add note, all without leaving Gmail
- Scheduler link insertion on Growth and higher
The add-on is not email sync, and the difference decides what gets logged
These are two separate mechanisms that people routinely conflate, usually after wondering why an email they sent is not on the record.
The add-on is a side panel. It reads and writes Pipedrive records from within Gmail, and its actions are the ones listed above: create a person, a deal, an activity or a note. It is a lens onto the CRM, and it does not by itself capture the correspondence.
Email sync is the mechanism that puts the messages themselves into Pipedrive, and Smart Bcc is the manual alternative for getting a specific message onto a record without syncing a whole mailbox. The distinction is visible in Pipedrive's own reporting: the Emails performance report in Insights measures emails sent and received through email sync or Smart Bcc, which is to say it measures the sync mechanisms and not the add-on.
The practical consequence is that a team running the add-on without sync gets tidy record-keeping and no correspondence history, which reads as the CRM losing emails. A team running sync gets the history and inherits a decision about scope, because syncing a mailbox brings in everything in it. Neither is wrong, and the choice should be made deliberately rather than discovered.
Where Gmail stops, in Google's own numbers
Google Workspace publishes its Gmail sending limits, and the figures below are from that page. Two framing notes from Google come first, because they change how the numbers behave: limits per day are applied over a rolling 24-hour period rather than a set time of day, and Google states plainly that sending limits can change without notice.
The headline figures for a Google Workspace user account:
| Limit | Value |
|---|---|
| Daily sending limit per user account | 2,000 messages (1,500 for mail merge, 500 for trial accounts) |
| Recipients per message | 2,000 total, maximum 500 external |
| Total recipients per day | 10,000 (1,500 for mail merge) |
| External recipients per day | 3,000 |
| Unique recipients per day | 3,000, of which 2,000 external (500 external for trial accounts) |
The line that governs outbound is external recipients per day, and specifically the unique-recipient figure. Google counts a unique recipient once per day no matter how many messages they receive, so the constraint on a prospecting programme is 2,000 distinct external people per mailbox per day at the absolute ceiling, and 500 on a trial account.
Ceilings are not operating levels. Nobody sends near a platform maximum to strangers and keeps a mailbox healthy, because volume from a cold sender is exactly the pattern spam filtering is built to catch. The practical daily figure for a warmed mailbox sending to people who did not ask is an order of magnitude below Google's ceiling, which is why outbound at any real scale is a question of how many mailboxes and domains you run rather than how much you can push through one.
Two more of Google's rules catch people building on top of Gmail. Messages sent from an alternate address or alias, by delegated users, or by Gmail's vacation responder all count toward the sending user's limits, so aliases do not multiply capacity. And the per-message recipient ceiling drops sharply depending on how you send: 2,000 in the Gmail interface, 500 via the Gmail API, and 100 via SMTP for POP or IMAP users or through GWSMO. A tool sending over SMTP is working against the hundred, not the two thousand.
Google also documents a limit increase that is not instant. Converting a trial to a paid subscription raises sending limits once the domain has cumulatively paid at least $100 USD or the equivalent, and Google states it can take up to 75 days after meeting that threshold for the increase to apply. A brand new domain bought for a campaign next week is on trial-account limits for a while.
- Depends: You are sizing against unique external recipients per day, not the 2,000 message figure
- Depends: You know that aliases, delegated users and the vacation responder all count against the same limit
- Depends: You know which send path you are on, since per-message recipients differ across interface, API and SMTP
- Depends: New domains are not assumed to be on full limits, given the $100 threshold and the delay after it
- Depends: Nobody is planning to run prospecting volume through the mailbox that carries customer correspondence
- Depends: Pipedrive's email sync allowance per user has been checked against the number of mailboxes the plan assumes
The architectural point the add-on quietly makes
The add-on is built for the mailbox a person actually uses. It surfaces CRM context beside real conversations, and every action it offers assumes a human is reading an email and deciding something. That is the correct use of a CRM inside an inbox.
Prospecting is a different job with different infrastructure requirements, and the separation is not fussiness. The mailbox where your account executives answer customers carries your contracts, your invoices, your renewals and your support threads. Sending cold volume from that identity puts all of it on one reputation, and a bad month in prospecting becomes a deliverability problem in commercial correspondence. Outbound belongs on its own domains and its own warmed mailboxes, structurally separate, so that the two workloads cannot damage each other.
Pipedrive's own plan limits nudge in the same direction. Email syncs are capped per user, moving from two to three per user across the Professional-to-Premium transition in the 2025 restructure, which is a number sized for a person's mailboxes rather than for a sending fleet.
The reply side is where the add-on earns its keep. When outbound is running on separate infrastructure and a prospect answers, the conversation moves to a real person's mailbox, and that is exactly the moment the Gmail side panel is useful: the rep sees who this is, what is open, and what was said, and creates the deal from the reply.
For the surrounding platform decisions, Pipedrive automation covers the workflow engine and its email-action constraints, Pipedrive dashboards and Insights reports covers what you can measure, best CRM tools for cold email teams covers the outbound CRM read, and best Pipedrive alternatives covers the exit. For the sending side that Gmail is not built to be, see what dedicated infrastructure produces.
Pricing and features verified as of August 2026. Verify current terms with the vendor before relying on them.
Frequently asked questions.
Frequently asked questions- What does the Pipedrive Gmail add-on actually do?
- It puts a Pipedrive panel in the Gmail sidebar. With no email open it shows the activities scheduled for today. With an email open it checks whether the sender exists in Pipedrive, offering to add them if not, and showing their details, deals, activities and notes if so. You can create deals, activities and notes from there.
- Why does the add-on fail to install with an unable to open file error?
- Usually because several Google accounts are signed into the same browser window, so Google authorises with the wrong session. Pipedrive names three fixes: install from an incognito window signed into only the intended account, sign out of all Google accounts and back into one, or create a dedicated Chrome profile for the work account.
- Does the add-on log my emails to Pipedrive?
- No, that is a separate mechanism. The add-on reads and writes records; email sync and Smart Bcc are what put the messages themselves onto a record. Pipedrive's Emails performance report measures emails sent and received through email sync or Smart Bcc specifically, which is the clearest sign that the add-on is not part of that path.
- How many cold emails can I send from Gmail per day?
- Google's ceiling is 2,000 messages and 2,000 unique external recipients per day per user account, applied over a rolling 24 hours. That is a maximum, not an operating level. Cold volume near a platform ceiling is exactly the pattern spam filtering catches, so outbound at scale is a question of how many mailboxes and domains you run.
About the author.
B2B cold email experts helping companies generate qualified leads through done-for-you outreach campaigns.
RevenueFlow Team
Explore more.
Ready to scale your outreach?
We build GTM engines that book real meetings. See the receipts.
Related articles.
Campaigns by Pipedrive: An Opt-In Tool, and What That Rules Out
Campaigns will not send to a contact without subscribed marketing status. What the add-on does, how it is billed, and why cold outbound belongs somewhere else entirely.
Pipedrive Integrations: Deciding Which System Owns Each Field
Every Pipedrive integration failure that costs money comes from two systems writing one field with no rule about who wins. How to settle that first.
Pipedrive MCP: Giving an AI Assistant Write Access to Your Pipeline
Pipedrive's native MCP server lets an assistant create and update CRM records. The permission model, the setup, and where it belongs against the API and the rules engine.
Pipedrive Dashboards and Insights Reports: Every Report Type and What It Answers
A dashboard is only as good as the Insights reports on it. The full catalogue of Pipedrive report types, what gates each one, and four picks for an outbound board.
The Pipedrive Essential Plan Is Now Lite: What Changed and Where the Limits Sit
Pipedrive renamed every plan in 2025 and moved the limits with them. The full mapping, the record and automation ceilings per tier, and the two lines teams misread.
Pipedrive Automation: The Trigger and Action Model, and the Rules That Silently Stop It
Pipedrive's automation engine fails quietly in four documented ways. The trigger and action vocabulary, the branching caps, and the behaviours that stop a workflow dead.