Four integrations under one name, all free to connect, each gated somewhere else.
Nothing on either side to connect. Click tracking needs an assigned Sales Hub seat; meeting prep needs Sales Hub Professional.
Contacts, Activities, Messages, Tasks, two-way sync.
This is four separate integrations wearing one name, which is why two people can both be right and disagree completely about what it does. A connected inbox, the Sales Chrome extension, calendar sync and the Google Sheets workflow action are different pieces with different requirements, and all four are free to turn on. What is not free is the half of each one teams assume comes with it: open tracking is on every plan and click tracking needs an assigned Sales Hub seat, calendar sync is on every plan and preparing for a meeting from inside Google Calendar needs Sales Hub Professional. Connect the inbox first, then buy a seat for the one feature you actually named.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Sent and received email | Both ways | A connected inbox sends one-to-one and sequence email from the CRM and logs replies back to the record. Available on all products and plans. |
| Email opens | One way, in | Tracked by the Chrome extension on Gmail web. With data privacy settings on, opens are tracked only for contacts carrying a legal basis for processing. |
| Link clicks | One way, in | Requires an assigned Sales Hub seat. Open tracking does not, and this is the only line on the table that separates them. |
| Calendar events | Both ways | Primary calendar only. Description edits made on the CRM record reach attendees on Google Calendar and on no other provider. |
| Tasks to the calendar | One way, out | HubSpot tasks appear on the connected calendar. Needs an assigned Sales or Service seat. |
| Rows into Google Sheets | One way, out | A workflow action writes up to 20 cells per row. Nothing in the sheet comes back to HubSpot. |
Two of those six rows move in both directions. The four that do not are Email opens, Link clicks, Tasks to the calendar and Rows into Google Sheets, and those are the rows that decide how you design around this rather than the ones in the brochure.
Nothing here is a field mapping in the usual sense. What matters is which surface a thing arrives on, and which of them are separate features that can fail on their own.
| In HubSpot | In Google | What to know about the match |
|---|---|---|
| Gmail message | Logged activity on the contact | Needs the sender to be a user, a connected address or a configured alias, or the message logs against nobody. |
| Open and click | Tracking events on the timeline | A separate feature from logging, needing an assigned Sales Hub seat, and it stops working on a customised Gmail layout. |
| Google Calendar event | Meeting on the record | One calendar only, matched by attendee. An attendee who is not a contact creates no association. |
| HubSpot task | Calendar event | Goes out to Google rather than coming back, so the calendar is a view of the task list rather than a second place to manage it. |
| Workflow output | A row in Google Sheets | A one-way pipe of up to 20 cells per action, not a sync. The sheet does not read back. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the five vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
Treat logging, tracking, calendar and the Sheets action as four separate integrations that happen to share a login, because that is how they break.
Three HubSpot editions against three Google ones, and what each pairing gives you. Pick the two you own and the grid marks the answer.
Pick an edition on each side.
| HubSpot seat | Gmail or Workspace | Workspace with Advanced Protection | Any inbox over IMAP |
|---|---|---|---|
| Free or View-Only | Connect and log | Not supported | Connect and log |
| Assigned Sales Hub seat | Plus open and click tracking | Not supported | Plus open and click tracking |
| Sales Hub Professional or Enterprise | Plus meeting prep and follow-up | Not supported | Plus meeting prep and follow-up |
Counted off that grid, of nine pairings: three give you not supported, two give you connect and log, two give you plus open and click tracking, two give you plus meeting prep and follow-up. The useful thing about this grid is how far down it the free column goes: connecting Gmail and logging mail is the one integration in this directory that costs nothing on either side.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
A conversation, not a screen
HubSpot will not let one email account be both an individual work email and a team email. Connecting support@ as somebody's personal inbox is the mistake that is annoying to undo, because the fix is disconnecting it and reconnecting it as a shared inbox after people have been logging against it.
Google admin console
A Gmail account enrolled in Google's Advanced Protection Program is not supported for an individual work email. Neither is a View-Only HubSpot seat, which is a licensing answer rather than a Google one.
HubSpot: Settings, General, Email, Connect personal email
Personal email access permission is required. Choosing Gmail runs OAuth against Google; choosing IMAP instead limits what HubSpot receives to the address, the password, server details, metadata and message bodies, and connects none of your other Workspace apps.
Chrome Web Store
The extension is what puts logging and tracking into the Gmail window. Email tracking and logging do not work with customised Gmail layouts, which is worth knowing before a rep tells you the extension is broken.
HubSpot: Settings, General, Calendar
The calendar integration syncs a single calendar, so a rep who runs a second shared calendar for customer sessions gets nothing from it.
HubSpot: the extension settings
For an email to log and create a contact, the sending address has to be a user in the account, a connected address, or a properly configured alias. A rep sending from an unregistered alias gets silence rather than an error.
Only the first step is an admin decision, and it is the only one that is expensive to reverse, which is a good argument for making it before the rollout email goes out.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-google/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-google.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyA View-Only seat, or a Gmail account enrolled in Google's Advanced Protection Program. Neither is supported for an individual work email.
Check the seat type first, since it is the one you can change. Advanced Protection is a Google policy decision and there is no HubSpot setting that works around it.
WhyThe same account is being used as both an individual work email and a team email, which HubSpot does not allow.
Disconnect it and reconnect it as a shared inbox. Decide which it is before the rollout, because the switch loses the arrangement people have got used to.
WhyThey are separate features. Tracking needs an assigned Sales Hub seat, and it does not work with customised Gmail layouts.
Check the seat, then have the rep turn off the custom layout in Gmail and retest.
WhyIt was sent from an address that is not a user, a connected address or a configured alias.
Add the alias in the connected inbox or in Profile and Preferences. Nothing errors when this is wrong, so it has to be checked rather than waited for.
WhyData privacy settings are on, and opens are only tracked for contacts with an assigned legal basis for processing.
That is a legal configuration rather than a bug. Your legal team decides the basis; the tracking follows it.
WhyThe integration syncs one calendar.
Move the meetings that matter onto the connected calendar, or accept that the other one is invisible to the CRM.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2022 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
We have an email address Support@ [...] This is connected to Hubspot. The problem, it is a user account
r/hubspot·November 2023·3 points
HubSpot documents that one account cannot be both an individual work email and a team email, and this is what that rule looks like when you meet it from the wrong side. It is the first step on the setup list for exactly this reason.
You can integrate your Gmail account directly with HubSpot, without the need for Zapier. That's if you want to also track the conversation history at the contact level.
r/hubspot·November 2025·4 points
A correction offered on a thread about automating Gmail leads with a third tool. On this pair the native route is both free and better, and the only reason to put an orchestrator in the path is logic the native connection does not do.
you can connect your own gmail or google workspace mailbox with hubspot and then download the hubspot chrome widget. Once installed you have the option to log and track all
r/hubspot·December 2023·5 points
Accurate, and worth separating: the connection carries the mailbox and the extension carries the logging and tracking buttons. When one rep has tracking and another does not, it is almost always the extension or the seat rather than the connection.
HubSpot Connector for Gemini is huge to be able to combine HubSpot data with your Google Drive data, with the 1M token context window
r/hubspot·September 2025·26 points
The most upvoted HubSpot and Google thread in the set is not about this integration. It is a separate connector aimed at Google's model rather than at Gmail and Calendar, and nothing on this page applies to it. Worth knowing before somebody forwards you the thread as evidence that the email integration got better.
It gives you about 80% of the outlook functionality just right out of the box. There are some
r/sysadmin·January 2022·6 points
Said about a different bridge, in a thread about running Google as the mail server behind Outlook, and it is the right expectation for mail integrations generally. The 20 percent on this pair is the second calendar, the custom layout and the alias nobody registered.
Two kinds of thread. One is people discovering that the native path already does what they were about to build with Zapier, which is the recurring theme on the cheapest integration in this directory. The other, newer one is about the HubSpot connector for Gemini, which is a different product entirely and is being discussed as though it were part of this integration.
Nothing in the threads argues against setting this up, which is unusual here, and it is what you would expect of an integration that costs nothing and logs mail correctly for most people on the first try.
The reason answers about this pair contradict each other is that there are four products behind the one name. Connecting an inbox, installing the Sales Chrome extension, switching on calendar sync and using the Google Sheets workflow action are separate integrations with separate requirements, and the feature somebody is asking about decides which one they are actually describing. The useful move is to name the feature before the tool: "we want to know who clicked" and "we want meetings on the timeline" have different answers and different bills.
All four connect for nothing, which makes this one of the few genuinely free integrations in the directory, and it is the reason the gates are easy to miss. The pattern is consistent once you see it: HubSpot gives away the data movement and charges for the sales feature built on top. Logging an email is free and knowing a link was clicked needs a Sales Hub seat; syncing a meeting is free and preparing for it from inside Google Calendar needs Sales Hub Professional. Neither of those is a subscription upgrade in disguise; a seat is a smaller purchase than a hub, and it is worth pricing that way round before anybody opens a quote.
The calendar limits are the ones that cost a quarter of reporting rather than an afternoon. Events from before you connected never come across, so the switch-on date becomes the start of your history whether or not anyone decided that. Worse, a guest who is not yet a contact will not be created, so the first meeting with a new prospect logs against nobody and the funnel that depends on it quietly undercounts. Both are documented and neither is configurable, which makes them planning facts rather than bugs: connect before the quarter you intend to report on, and keep a route that creates the contact first, usually a Clay table.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Google and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Yes. The HubSpot Gmail integration runs on all products and plans, and connecting a personal inbox is the piece everything else depends on. You need the Personal email access permission, a View-Only seat cannot connect one at all, and the Gmail account has to be unique to you because HubSpot will not let one address serve as both a personal inbox and a team inbox. Gmail accounts enrolled in Google's Advanced Protection Program are not supported, which is worth checking before you promise a date to a security team.
For opens, no. For link clicks, yes: HubSpot documents click tracking as requiring an assigned Sales Hub seat, while open tracking runs on every plan. That one line is the whole paid-versus-free question on this pair, and it is a seat assignment rather than a subscription upgrade, so the fix is usually cheaper than the conversation suggests.
Partly, and the exceptions matter more than the headline. Calendar sync reads only your primary or default calendar, so a rep who keeps client meetings on a second calendar syncs nothing. You can run the Google calendar sync or the Outlook one, never both. Events created before you connected do not come across, private events never do, and a recurring series syncs the next five upcoming events up to a year ahead. Editing a meeting description on the CRM record and having attendees actually receive it is a Google Calendar behaviour and does not happen on Outlook.
Yes, through a workflow action, and it is narrower than people expect. Each action writes up to 20 cells of data per row, the sheet's header row has to start in the first column of the first row, and HubSpot cannot send data to an unlabelled column. HubSpot also advises one workflow per sheet, because two workflows writing the same sheet duplicate data. If you need the date formatted before it lands, the Format data action that does it is a Data Hub Professional feature.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.