---
name: hubspot-google-integration
description: Connect HubSpot and Google Workspace: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, activities, messages, tasks. Use when the user wants to set up, audit or troubleshoot HubSpot and Google together, or asks why data is not moving between them.
---

# HubSpot and Google Workspace

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-google-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** Nothing on either side to connect. Click tracking needs an assigned Sales Hub seat; meeting prep needs Sales Hub Professional.

**What moves:** contacts, activities, messages, tasks, both ways.
**How it is built:** native, marketplace app. **Effort:** minutes.

## The short version

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.

## Check the plan before anything else

Rows: HubSpot seat. Columns: Google account. Most of the reports that this integration is broken are a pairing from this grid that was never going to work.

| 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 |

- **Not supported.** A Gmail account in Google's Advanced Protection Program cannot be connected as an individual work email at all. A HubSpot View-Only seat cannot connect one either, for an unrelated reason with the same outcome.
- **Connect and log.** Connecting the inbox and logging messages to the CRM costs nothing on either side. This is the half most teams think they are buying.
- **Plus open and click tracking.** Opens and clicks need an assigned Sales Hub seat. It is a seat question rather than a tier question, which is why it varies between two people on the same plan.
- **Plus meeting prep and follow-up.** Preparing for upcoming meetings, following up on past ones and logging the meeting type all need Sales Hub Professional or Enterprise.

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.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Sent and received email | Two-way sync | 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 | Two-way sync | 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. |

## Which field lands where

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. |

**What does not cross:**

- Anything from an account on Google's Advanced Protection Program, which HubSpot does not support for an individual work email.
- Opens from contacts with no legal basis for processing, once data privacy settings are on in the account.
- A second calendar. The integration reads exactly one.

## Connect it, in this order

**Who has to do it:** Each user connects their own inbox. Nobody can do it for them, and a View-Only seat cannot do it at all.
**How long:** Five minutes per person, plus one decision an admin should make first.

### 1. Decide which inboxes are personal and which are shared, before anybody connects

*Where:* 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.

### 2. Check the account is one HubSpot can take

*Where:* 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.

### 3. Connect the inbox

*Where:* 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.

### 4. Install the Chrome extension for the people who want tracking

*Where:* 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.

### 5. Connect the calendar, and know it reads one

*Where:* 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.

### 6. Set what logs by default, then check the aliases

*Where:* 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.

## How to check it worked

- Send a tracked email to yourself from a rep account and confirm both the log and the open register. Logging and tracking are separate features and they fail separately.
- Check that the contact timeline shows the message against the right contact rather than creating a second one.
- Put a meeting in the connected calendar with an external attendee and confirm it lands on the contact record.
- If your account has data privacy settings on, test with a contact that has a legal basis set, because opens are only tracked for those.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| A rep cannot connect their inbox at all | A 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. |
| Emails from the shared address stopped logging properly | The 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. |
| Logging works and tracking does not | They 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. |
| An email logged against nobody | It 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. |
| Opens are not registering for some contacts | Data 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. |
| Meetings from the second calendar never arrive | The integration syncs one calendar. | Move the meetings that matter onto the connected calendar, or accept that the other one is invisible to the CRM. |

## What breaks, from the vendors' own docs

- **Calendar sync reads exactly one calendar.** Only the primary or default calendar syncs. A rep with a separate client calendar gets nothing from it, and there is no setting that adds a second one. You also choose between the Google calendar sync and the Outlook one; HubSpot will not run both at once, which is a real constraint in companies that have half migrated.
- **A meeting with a stranger logs against nobody.** HubSpot will not create a contact record for a calendar guest who is not already a contact, and a guest only receives the meeting if the address on the invite matches the Email property on their contact record. So the first meeting with a new prospect, the one you most want on a timeline, is the one most likely to land nowhere. Private events never sync, and a recurring series brings across the next five upcoming events up to a year in advance rather than the whole series.
- **Tracking stops at the browser.** Opens and clicks are tracked by the Chrome extension on Gmail web. Mail sent from the Gmail mobile app or any other client is not tracked, though the BCC address still logs it. Emails using customised Gmail layouts are not supported at all. Attachments over 50 MB are delivered and do not log, and turning logging on does not log anything you sent before you turned it on.
- **The Sheets action is a 20 cell pipe, not a sync.** Each workflow action adds up to 20 cells of data per row, the header row must begin in the first column of the first row, and unlabelled columns receive nothing. HubSpot recommends a single workflow per sheet because two writing the same one duplicate data, and warns that formula-heavy sheets slow the action down or make it error. Formatting a date before it is written needs the Format data action, which is Data Hub Professional.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- HubSpot knowledge base: connect your personal email: https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot
- HubSpot knowledge base: track and log emails with the Sales Chrome extension: https://knowledge.hubspot.com/connected-email/track-and-log-emails-with-the-hubspot-sales-chrome-extension
- HubSpot knowledge base: calendar sync with Google Calendar or Outlook: https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-google-calendar-or-outlook-calendar
- HubSpot knowledge base: manage meetings in Google Calendar with the Chrome extension: https://knowledge.hubspot.com/connected-email/manage-your-meetings-in-google-calendar-with-the-hubspot-sales-chrome-extension
- HubSpot knowledge base: add data to Google Sheets with workflows: https://knowledge.hubspot.com/workflows/add-data-to-google-sheets-with-workflows
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-google-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-google-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
