Google adds Adobe, Squarespace and Peloton to Gemini Connected Apps

What happened

Google has widened the set of third-party services its Gemini assistant can act on, adding Adobe, Squarespace and Peloton among a new batch of Connected Apps. According to a dev.to article covering Google's announcement, the rollout started on September 23, and is meant to let people pull supported apps into a Gemini conversation and carry out relevant actions without switching away from the chat.

Google organizes the new partners into three groups. The productivity category includes Airtable, Linear, monday.com, PandaDoc, Wispr AI and Zoho. The creativity group covers Adobe, Picsart, Squarespace and Webflow, with Adobe positioned around asset creation and Squarespace around website design. The lifestyle group lists Peloton, apartments.com, Experian and SeatGeek, with Peloton tied to workout planning.

How the integrations work

Connected Apps are designed to turn Gemini into a place where a natural-language request can draw on a linked external service. The mechanics, as described in the dev.to report, are simple on the surface: a user connects an available app through Gemini's settings, then brings it into a conversation either with an @mention or by referring to it directly in a prompt.

Peloton offers the most concrete illustration of the model Google is pursuing. The company says Gemini users can plan workouts inside chats and prompts, meaning the request starts as ordinary conversation and ends with an action carried through the connected service rather than a separate app.

What is and is not confirmed

The announcement confirms an ecosystem expansion, not a full feature set for every partner. Google has not spelled out the specific commands, workflows or capabilities each integration exposes, so the confirmed news is that these services are now part of the Connected Apps program, not that Gemini can perform every task within each platform. Whether a given action works will depend on the individual app and the functions it makes available through its Gemini integration.

Two other gaps are worth noting. Google has not published pricing details for the expansion, and beyond saying the rollout began September 23, it has not laid out a universal availability schedule.

What organizations should weigh

For teams, the immediate question is not whether to connect everything on the list but which repeatable tasks could realistically start inside Gemini instead of in a search box, a bookmarked tab or a manual copy-and-paste between tools. Creative teams might watch how Adobe's connection handles asset-related work; site owners can test where Squarespace or Webflow fits their design and publishing process; teams already using Airtable, Linear, monday.com, PandaDoc or Zoho can check whether connected prompts match their planning and documentation habits.

Because activation happens at the level of Gemini settings, the dev.to article also raises a governance point: organizations should decide which users test these integrations early and which existing workflows are appropriate for that testing. There is also a practical caution against assuming an integration replaces an established process outright. The more useful test is whether pulling an app into Gemini genuinely improves a specific task, such as moving from a content idea to an asset workflow. Trying a small number of well-defined use cases will reveal more than connecting tools without a purpose.

Why it matters

The expansion signals that Google is positioning Gemini less as a standalone chat product and more as a coordination layer across the software people already use for work and personal tasks. The partner list now spans work management, creative production, web design, fitness and consumer services, which makes Connected Apps look like a platform strategy rather than a narrow add-on.

If the model works, workflows that currently begin with searching, switching tabs or manually transferring context between applications would increasingly begin in a single conversational interface. That shift would matter for competitors building assistants, for the app vendors deciding how deeply to integrate, and for users deciding how much of their toolchain they are willing to route through one assistant. Much depends on execution details Google has not yet published: the depth of each integration, reliability of the routed actions, and how availability and pricing unfold beyond the initial rollout.