A custom function gets 30 seconds. A script gets six minutes. A live job can take tens of them.
- Moves: Contacts, Companies, Custom objects
- Needs: A Google account, a Reverse Contact API key, and Apps Script or an orchestrator that can read the sheet
Three integrations, two of them free, and one finding that turns up in both: a Google Calendar integration here reads the primary calendar and no other. HubSpot and Slack document that limit independently.
Gmail and Calendar, the most-installed connectors in B2B.
Gmail and Calendar are not sales tools, and they are the most consequential integrations in most stacks anyway, because they decide whether activity data exists at all. They are also the two most installed connectors on the HubSpot marketplace by a wide margin. That is why this hub spends its time on what they do not cover rather than on what they do.
The finding worth carrying away is the one both vendors document separately. The HubSpot integration syncs only the primary or default calendar, and the Slack integration syncs status with the primary calendar of the connected account and no other. A rep who keeps client meetings on a second calendar is invisible to both, and no setting on either side adds one.
The third route is the one teams actually build on. A spreadsheet is the only surface in this directory that can send a request, read the answer and do it with no plan upgrade on either side, which is why so many enrichment pipelines live in one. It is also why so many of them quietly break, because a sheet has no row locking and a row number is not an identity.
Google Workspace sits in the collaboration layer, with 2 other tools in this directory. Counted across the whole directory it reaches 3 of the other 22 tools, and the integration matrix shows that row against every other.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for freeA custom function gets 30 seconds. A script gets six minutes. A live job can take tens of them.
Four integrations under one name, all free to connect, each gated somewhere else.
An admin installs it once, then every person has to connect their own account.
4 things that decide whether a Google Workspace integration will work for you, in the order they usually bite.
A connected inbox, the Sales Chrome extension, calendar sync and the Google Sheets workflow action are separate things sold under one label, which is why two people can both be right and disagree completely about what the HubSpot integration does. Nothing on either side is needed to connect them, but click tracking needs an assigned Sales Hub seat and meeting prep needs Sales Hub Professional. Work out which of the four you are talking about before pricing anything.
HubSpot syncs only the primary or default calendar, and Slack syncs status with the primary calendar of the connected Google account and no other. Two vendors documented the same limit independently, which makes it a property of the way Google calendar access works rather than a gap either of them is about to close. A rep with a separate client calendar gets nothing from either integration, and there is no setting that adds a second one.
An admin installs the Drive and Calendar apps for the Slack workspace, and then every member who wants it connects their own Google account. Nothing about the admin screen suggests the second step exists, which is why this integration is declared finished more often than it is actually finished. Domain-wide authentication needs two admins to authorise it. Check adoption per person rather than per workspace.
A custom function gets 30 seconds and a script gets six minutes, and both figures are the same on a consumer account and on Workspace, so there is no plan that buys more time. UrlFetch is 20,000 calls a day per user, or 100,000 on Workspace, and time-driven triggers get 90 minutes of total runtime a day, or six hours. Those are the real budgets for an unattended sweep. What breaks a sheet pipeline is rarely the quota though: it is that two runs writing the same row produce one surviving value and no error.
Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.
A custom function gets 30 seconds. A script gets six minutes. A live job can take tens of them.
One way, in → 02Four integrations under one name, all free to connect, each gated somewhere else.
Two-way sync → 03An admin installs it once, then every person has to connect their own account.
Two-way sync →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.
Free trial, no card required, and 500 credits to start.
The questions that come up before anyone opens a setup guide.
No, and both vendors in this directory document it separately. The HubSpot calendar sync covers only the primary or default calendar, and Slack syncs status with the primary calendar of the connected Google account and no other. A rep who keeps client meetings on a separate calendar is invisible to both, and there is no setting on either side that adds one.
Four things sold under one name: a connected inbox, the Sales Chrome extension, calendar sync and the Google Sheets workflow action. Connecting costs nothing on either side. Click tracking needs an assigned Sales Hub seat and meeting prep needs Sales Hub Professional, and tracking stops at the browser, so mail sent from the Gmail mobile app or any other client is not tracked.
Yes, through Apps Script, and it is the only surface in this directory that can do it with no plan upgrade on either side. A custom function gets 30 seconds and a script gets six minutes, the same on a consumer account as on Workspace. UrlFetch is capped at 20,000 calls a day per user, or 100,000 on Workspace, and time-driven triggers get 90 minutes of total runtime a day, or six hours on Workspace.
Usually not because of a quota. A sheet has no row locking, so two runs writing the same row produce one surviving value and no error, and a run that dies halfway leaves rows that look pending and are not. A row number is also not an identity: sorting a sheet, inserting a row or filtering it moves every row below the change, so an answer addressed to row 412 lands on whoever is sitting there when it arrives.
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.