Now you can connect even more of your favorite apps and services to Gemini.

What happened

I'll pull the official Keyword Blog post and the site's post rules so the piece stays factual and matches how TechBytes writes standalone news.Google’s Keyword Blog says you can now connect even more of your favorite apps and services to Gemini, wiring those services directly into the assistant so it can help plan trips, manage projects, and work through a daily to-do list. Mai Lowe, Group Product Manager for the Gemini app, framed the news at Made by Google as a new slate of connected apps you turn on inside Gemini, with planning, creating, and task work meant to happen in one place as the connections roll out over the following weeks. Granola, Otter.ai, and Wix cover productivity and creativity, including meeting summaries and website edits. Fever, GetYourGuide, Localiza, OpenTable in the UK, and Ticketmaster cover local and entertainment work such as booking experiences, renting a car, reserving dinner, and searching for event tickets. iHeartRadio and Pandora cover stations and playlists. Angi, Thumbtack, and Zocdoc cover finding a home professional and booking a doctor. This is a wider connected-app catalog, not a new Gemini model.

The mechanic is an opt-in connection. You turn a service on inside Gemini, then Gemini can use that service when a prompt needs it, so the chat becomes the front door for work that used to start in each vendor’s own app. Trip planning maps to the travel and local partners: experiences, cars, dinners, and tickets are named actions, which is how one thread can move from a plan toward a reservation without a copy-paste across tabs. Project work maps to the productivity partners: meeting notes in Granola or Otter.ai and a site in Wix are the systems of record, and Gemini is positioned as the layer that can summarize or edit them in place. The daily to-do list is the rest of the day, from a home visit to a doctor booking to a playlist. Google does not publish an API version, a connector SDK, or a protocol name in this post. What users see is the existing Connected Apps control, now aimed at a longer catalog, plus a support page for turning those links on and off.

The technical detail

For engineers and builders this is a tool-use and distribution problem. An assistant that cannot reach the app that holds the meeting, the itinerary, or the ticket is a drafting box. An assistant that can is an operator sitting on other products’ read and write paths. The design work is the connection layer, the permission prompt, and the action boundary: which tools the model may call, what it may read, what it may change, and how the user revokes that. Google is making that choice a per-service toggle. Teams shipping internal copilots should take the job list in the announcement and map it onto their own stack. Meeting notes, site edits, bookings, and task closeout are the jobs. The connector is the product. If your agent still asks someone to paste a transcript or open another tab to finish a reservation, you are behind the shape of this Gemini surface.

Why it matters for builders

The market fight is over which assistant becomes the session start, then reaches into apps people already pay for so they do not have to leave. Google already has Search, Maps, Workspace, and the Gemini app. Adding Granola, Otter.ai, Wix, Ticketmaster, OpenTable, Zocdoc, and the rest is how that start screen stops being a Google-only loop. Rivals have run the same play with plugins, workspace add-ins, and third-party connectors. The Keyword Blog language is consumer-simple, but the move is a catalog war. Partners that connect become capabilities Gemini can offer in-thread. Partners that stay out become destinations the user must abandon Gemini to visit. Who appears in Gemini’s connected list, and who does not, is a clearer signal than a keynote line.

Market and competitive context

The useful next step is to test the three jobs Google named. This post does not give a version string. If you use Gemini, open Connected Apps, enable the services you already live in, and run one trip prompt, one project prompt, and one to-do prompt against real data. Check whether Gemini can summarize a real meeting from Granola or Otter.ai, whether it can touch a Wix site, whether a dinner, ticket, car, or local experience can be reserved without a handoff, and whether Angi, Thumbtack, or Zocdoc actually complete the chore. If you build on Gemini or beside it, treat those results as acceptance tests. A read-only summary is a different product from a confirmed write. As this slate rolls out over the coming weeks, the result that matters is how many of those jobs finish inside the thread.

What to watch next

The Keyword Blog post leaves the hard questions unnamed. It does not say how consent is scoped per service, how long connected content lives in a Gemini conversation, what a user sees when two apps disagree about a reservation, or what happens when a connected write fails halfway. It does not give a partner count beyond the names above, a price, a full region list beyond the OpenTable UK note, or an API revision. Those gaps are the risk surface. Earlier assistant extensions promised to live in your other apps and then stalled on auth friction, shallow read access, and partners that never shipped a write path. Connecting more favorite apps only changes the product if the new links can plan the trip, move the project, and close the to-do without sending the person back out to finish the job by hand. Until those paths are exercised on real tasks, treat the announcement as a catalog expansion and verify each connection yourself.