Google previews one app integration for Search and Gemini
Edited and reviewed by AI Ping Editorial Team
3-line summary
- Google previewed a shared app integration platform for Search and Gemini.
- Developers test an app and submit it to Google before publication.
- Search currently supports US English, with requirements varying by app.
Google opened a preview of its Connected Apps developer platform on October 28, offering one integration path into Search and Gemini. Developers can submit an app for either product or both. Access is being granted in phases through a preview application process.
Connected apps give AI conversations access to live information and actions from services a user has authorized. Google’s platform overview says linking a service account once lets that connection work across applicable Google products. For developers, the shared integration path reduces separate product-specific work. For users, linked account information can provide context for requests made inside a conversation.
The implementation depends on where an app’s functions run. Google recommends a server-based Model Context Protocol integration as the default for cross-platform services, covering Android, iOS and the web. MCP provides a way for AI to call external tools. A complementary Android route exposes app functions on the device, supporting access to local content and deeper operating-system capabilities. Users can invoke a connected app by mentioning its name or using @ followed by the name. It remains in context for relevant follow-up requests in that session.
Businesses submitting server-based integrations need a publicly accessible secure server, a developer account and proof that they control the service’s domain. Google’s prerequisites require an account owner or administrator to accept the program agreement before teammates can proceed. Submission materials also include public terms and privacy-policy addresses, descriptions of useful tasks and examples of questions the app can handle.
Testing precedes review and publication
Registration takes place in Google Connected Console. An unpublished app is visible only to designated testers, who can check authentication, tool execution and confirmation prompts before review. After approval, the developer selects Publish to start distribution across the chosen Google products.
Apps using personal service accounts go through sign-in and permission approval. Google’s authorization guide describes the service’s authentication server verifying the user and obtaining consent before passing back the information needed for access. Google recommends OAuth 2.1 with PKCE, which protects the authorization-code exchange. The integration also supports a revocation endpoint for disconnecting an account.
Google’s app policy limits what data and actions an integration may request. Apps must seek only the data and permissions necessary for their features, disclose collection purposes and explain how users can delete their data. Data use must follow the purposes disclosed to users, and the integration must function reliably without authentication failures or timeouts. Unsolicited actions and unexpected side effects are prohibited. Third-party advertising through the integration is also prohibited, with rejection, suspension or removal among the possible enforcement outcomes.
The console sets countries, languages and Google products for each version. Developers can require confirmation before a tool runs; that option is preselected for tools marked as destructive. Requests for additional context, including precise location, need a clear functional purpose.
Availability differs between products. Search’s help page currently limits Connected Apps in AI Mode to the United States in English. Users must sign in to Google, and some services require their own linked account. Certain tasks finish in the partner app: Instacart handles grocery checkout and order management, while Canva handles editing and downloading designs.
Gemini applies app-specific location, language, age and account requirements. Adobe, for example, requires a personal Google Account and an age of at least 18, supports English, and is available where both Gemini and the service operate. Google also says the set of connected apps can vary between web and mobile devices. Experian and Peloton are listed for personal-account users aged 18 or over in the United States, in English. Individual services retain their own signup requirements.
Adobe, Experian, Localiza and Peloton are already available in Gemini, with Search support planned in the coming weeks. Calm is planned for both. Google intends to expand developer access, markets and supported products over the coming months.
Sources
- Connected Apps preview — October 28, 2026 — Google
- Connected Apps overview — Google for Developers
- MCP integration environments — Google for Developers
- Registration prerequisites — Google for Developers
- Registration, testing and publication — Google for Developers
- User authorization — Google for Developers
- Connected Apps policy — Google for Developers
- Connected Apps availability in Search — Google Search Help
- App availability and requirements — Gemini Apps Help