Gemini Can Now Read Your CRM and Books. It's On by Default.

On September 15, 2026, Google quietly gave Gemini a set of keys to seven tools most small businesses already run: HubSpot, Salesforce, QuickBooks, Mailchimp, Asana, monday.com, and Atlassian's Rovo. Ask a question inside Gmail, Docs, Sheets

On September 15, 2026, Google quietly gave Gemini a set of keys to seven tools most small businesses already run: HubSpot, Salesforce, QuickBooks, Mailchimp, Asana, monday.com, and Atlassian's Rovo. Ask a question inside Gmail, Docs, Sheets, or Chat, and Gemini can now reach into whichever one of those systems has the answer and hand it back to you without you opening a second tab. It shipped switched on, for every user with Gemini access, with no setup screen to click through first.

That "on by default" part is the headline every recap of this launch buried under a list of logo names. If you run a small business on Google Workspace and any one of those seven tools, Gemini already has a live connection to your customer data, your books, or your project board right now, whether you asked for it or not.

What actually shipped on September 15

The mechanism is Model Context Protocol (MCP), the same connector standard Anthropic uses for Claude. Google's own announcement describes it as letting Gemini "access information directly without needing to switch tabs, download files, or interrupt workflows" across Sheets, Gmail, Drive, Docs, and Chat. In practice: ask Gemini in Gmail to pull up a contact's open deals and it queries Salesforce or HubSpot live. Ask it to check whether an invoice cleared and it checks QuickBooks. Ask it what's blocking a project and it reads the board in Asana or monday.com.

Admins aren't locked out of the decision. Every connector can be restricted or switched off at the domain, organizational unit, or group level from the Admin console, under Apps, Google Workspace, Gemini for Workspace, Third-Party Connectors. It's just that the default Google chose was on, not off, which means the businesses actually making that choice deliberately are the minority.

It's read-only, and that's the detail worth getting right

Before this turns into another "AI vendor secretly wired itself into your data" story, the accurate version is less alarming than the headline suggests. Google's own support documentation is specific: "Integrations currently only support read actions, such as searching for or finding information. You can't use an integration to make changes to third-party apps." Gemini can look up a HubSpot deal. It cannot update the deal stage, delete a contact, or send a Mailchimp campaign. And it respects whatever permissions already exist in the source system: a rep who can't see a record in Salesforce still can't see it through Gemini. HubSpot's own knowledge base confirms the same boundary on its end, stating that the connector doesn't override existing security settings and that record-level permissions and data visibility rules still apply.

Two AI vendors wired into your stack on the exact same day

Here's the detail no single-vendor writeup of this launch seems to have caught: September 15 wasn't just Google's day. It's the same date Anthropic expanded Claude for Small Business from 15 to 43 workflows and added 27 new connectors, including Shopify, TikTok, Zoom, Xero, Gusto, Square, Stripe, Zapier, Atlassian, and Salesforce, a launch we covered in detail here. Two of the biggest names in AI both raced to embed themselves natively into small-business software on the same Tuesday, and both picked Salesforce and Atlassian as overlapping targets.

Anthropic shipped 27 connectors in approval mode, so nothing runs until you say go. Google shipped 7 connectors already running, and the only action they take is looking things up. Neither company is wrong to build this. They just made opposite bets on what a small business owner would rather discover for themselves: a longer list of things to turn on, or a shorter list of things they never got asked about.

— our automation lead, comparing the two launches side by side

Neither company is racing because small businesses were clamoring for a faster way to check a HubSpot record from inside Gmail. They're racing because whichever assistant is already sitting inside your inbox when you need an answer from your CRM is the one you'll keep opening tomorrow. Read our breakdown of Gemini's Ask Gemini in Chat rollout from three weeks earlier for the pattern this fits: Google keeps pushing Gemini deeper into the tools your team already has open, one release at a time.

Zoom out further and September 15 gets crowded fast. The same day Google shipped its seven MCP connectors, Salesforce's own Dreamforce keynote confirmed Gemini going generally available inside its Agentforce Reasoning Engine, deepening a Google Cloud partnership announced that same day. It's also the week Claudeforce, the Salesforce-Anthropic plugin we covered when it first landed in pilot, moved toward the wider open beta Salesforce had promised. HubSpot followed one day later, on September 16, with its own AI agent stack. Four companies shipped four different ways of putting an AI assistant next to your customer data inside a single week. Anthropic and Google are pushing their assistants out into your tools. Salesforce and HubSpot are pulling outside assistants into their own products. If you run a small business on any combination of these platforms, you didn't ask for four companies to start reasoning over your customer data in the same week, but that's what happened.

The real question isn't "is it safe," it's "is it actually useful yet"

A read-only lookup across seven tools sounds like exactly what a busy owner wants until you try to use it for something that matters. Ask Gemini to pull up "the Henderson deal" and it needs to know which system Henderson lives in, whether there are duplicate contact records for Henderson across HubSpot and Salesforce if you're unlucky enough to run both, and whether the deal stage in the CRM is even current. None of that is Gemini's fault. It's the same data-hygiene problem we flagged in HubSpot's own AI agent launch the week before this one: an assistant that reads your CRM is only as reliable as the CRM it's reading. A lookup tool built on duplicate contacts and three-month-stale deal stages will confidently hand back a wrong answer just as fast as a right one.

The other limit is the read/write line itself. Gemini can tell you an invoice is 40 days overdue. It can't send the reminder, adjust the payment terms, or flag the account for collections without a person doing that part by hand. That's a real ceiling on how much time this actually saves day to day, and it's worth being honest about before anyone budgets it as a productivity win.

What to actually check before you trust it

Four things are worth doing in the next week if you're running Workspace with any of these seven tools connected, none of which require waiting on Google or a vendor to fix anything for you.

First, open the Admin console and see which connectors are live for your organization right now, since the default is on and you may not have made that decision consciously. Second, check whether the tools it's reading are actually clean: the same duplicate-contact and stale-deal-stage problems that make CRM AI agents unreliable make a read-only lookup tool unreliable too, just with lower stakes per mistake. Third, decide as a team whether pasting what Gemini surfaces into a shareable doc needs a second look before that doc leaves your domain, since the connector's permission model doesn't follow the data once it's copied somewhere else. Fourth, if what you actually wanted was for something to run automatically instead of being looked up and read by a person, this isn't that tool, and it's worth being clear internally about which problem you're solving before you tell your team to "just ask Gemini."

That last one is the actual dividing line we see most often: owners conflate "I can find this faster" with "this now happens without me," and those are two different builds with two different price tags. A lookup layer is worth having. A reconciliation that runs itself, a follow-up that sends itself, a lead that gets scored and routed without a person touching it, that's automation, and it's a different project than turning on a connector Google already turned on for you. It's also the build we actually do: audit what's already connected, decide what should stay read-only versus what's worth wiring into a real workflow, and only then start automating.