Google opens Connected Apps Platform preview for services inside Search and Gemini

Google opened a preview of its Connected Apps Platform on October 28, 2026, giving developers one place to build and manage connections between their services, Search and the Gemini app. Access is opening in phases, with more developers and markets planned. For Israeli software companies and service businesses, it offers a possible route to bringing a business action into an AI conversation, subject to admission, review and availability.

The announcement concerns the service behind the answer: access to account information and task completion through an approved connection. Businesses considering it need to define what customers can do, what data is required and where presenting an option ends and taking action begins. Connecting does not guarantee a brand recommendation or favored search placement.

One connection for two Google environments

Developers can use a cloud-hosted MCP server or Android MCP through AppFunctions APIs, Google says. MCP is a protocol for connecting tools and information to AI systems. Google presents the platform as a way to reduce separate integrations, with developers choosing Search, Gemini or both as destinations.

Google Connected Console handles registration, testing and submission for review. The company says developers can then monitor traffic, response time and error rates, and manage brand identity through verified logos and authenticated accounts. A successful connection consequently needs ongoing operations, extending beyond the first working test request.

For an Israeli team already running an online service, the starting point is an existing capability customers understand and need. Hypothetically, retrieving an order's status from an authorized account is more defined than asking an assistant to manage the entire customer relationship. A clear action makes missing data and expired permissions easier to test.

Personal information and actions need clear boundaries

Google's documentation explains that users link an app to access live account context and service actions within a conversation. The cloud connection includes documentation for OAuth 2.1, an authorization mechanism that lets a service operate within access granted by the user. This does not authorize transferring everything held in the business's systems.

Platform policy requires data and permissions to be limited to what active functionality needs. It also prohibits requesting or collecting user prompts, the full conversation context or conversation history. A company therefore cannot treat the integration as a route to a complete dossier on the person. It must determine what the particular request requires.

Operational planning should separate retrieving information from changing it. Reporting an order's status and canceling that order are different actions. Even inside the same conversation, they require distinct planning for permissions, approvals and records. This is a design recommendation reflecting their consequences, not a promise that Google resolves every operational decision.

Google sets conditions for connected apps

The policy reviewed requires reliability, accurate capability descriptions and behavior consistent with user intent. Tool operations must be declared in the console in advance, with specified annotations or human confirmation for sensitive irreversible actions. Misleading descriptions designed to make a model select one app over another are prohibited.

That directly affects marketing: descriptions and buttons should promise functionality the service delivers. A capability needs to explain the actual action. A service offering availability checks should return availability; one creating an order should clarify what will be created. Overbroad promises can undermine usability and policy compliance alike.

Google also prohibits third-party advertising through integrations and requires independent practical utility. The reviewed policy additionally prohibits integrations that proxy to other AI agents acting autonomously. These restrictions matter to companies considering moving an existing automation system onto the platform. Technical protocol compatibility alone is insufficient.

Announced partners and a continuing rollout

Google said more than 50 Connected Apps had launched across Search and Gemini, covering areas including productivity, event tickets, health and fitness. Adobe, Experian, Localiza and Peloton were named as integrations live for Gemini users, with Search availability planned for subsequent weeks. Calm was described as an upcoming integration for both environments.

The timing distinction matters: plans to bring an integration to Search do not establish current availability for every user. Nor does the overall partner count establish availability in Israel. Before committing to customers, Israeli businesses should check supported markets, languages and account types, together with the status of their application.

As of the November 5 source check, this article does not confirm any particular Israeli company's admission or launch date. It also contains no local launch usage or conversion data. The opportunity to apply for preview access allows businesses to investigate suitability; individual approval remains a separate step.

The connection to GEO starts with user needs

The platform presents two complementary jobs: explain the business clearly and deliver a reliable action when needed. When planning a presence in generative engines, clear content helps people understand the offer. An app integration concerns task completion. The reviewed sources contain no formula guaranteeing that combining the two produces recommendations.

Service pages should not be replaced with a broad claim that the business is already inside AI. The website still needs to explain suitability, conditions and support. The connected app must deliver an answer or action consistent with that explanation. A mismatch creates confusion even when each experience looks effective independently.

The discussion about brand recommendations from AI assistants gains a practical dimension: what the user can complete after seeing an answer. Nevertheless, integration operations and brand visibility measure different things and should be assessed separately.

Success should also be defined from the customer's perspective. Receiving a request does not always mean completing it, and confirmation must reflect the business system's actual status. Decide what status returns to the conversation and who explains any pending work.

What to prepare before applying

A reasonable first step is choosing one action, defining its outcome and identifying the minimum information required. Prepare scenarios involving success, missing data, unauthorized users and duplicate requests. These are suggested tests, not additional product requirements announced by Google. They reveal whether a service can handle conversations that diverge from expectations.

Decide who handles errors and who can stop a malfunctioning integration. The news is a unified route for services inside Google's products. For Israeli businesses, the opportunity begins with a useful, clearly defined capability and evidence that it works within boundaries both the customer and the business understand.