# Google: Sheets, Gemini Enterprise and Custom Agents

Choose the Google product that matches the job. Sending records to Google Sheets, asking Gemini Enterprise a question and deploying a custom agent on Google Cloud require different setup.

## Google reference architecture

[![SiteTrax.io and Google reference architecture: capture, storage and specialized SiteTrax models create records; configured output sends data to Google Sheets, while proposed Gemini Enterprise and custom ADK agent paths use the SiteTrax MCP endpoint. Agent Runtime is a proposed host and business-system actions require separate authorization.](https://docs.sitetrax.io/uploads/images/gallery/2026-10/scaled-1680-/08-google-integration-architecture.png)](https://docs.sitetrax.io/uploads/images/gallery/2026-10/08-google-integration-architecture.png)

[Open the Google architecture diagram at full size](https://docs.sitetrax.io/uploads/images/gallery/2026-10/08-google-integration-architecture.png). Solid arrows show the documented data path. Dashed paths require SiteTrax.io validation or a scoped implementation. The Google Cloud project owner, billing owner and support responsibilities must be agreed for a custom agent deployment.

### Where Gemini fits

SiteTrax.io’s specialized detection and identifier-reading models create the asset observations. SiteTrax-managed processing can use Google Cloud compute, but that compute is separate from the agent layer. In the proposed agent path, Gemini interprets the task, ADK coordinates authorized tools, and Agent Runtime is a hosting option. The agent can combine SiteTrax.io evidence with separately authorized business data and actions.

For example, a user asks when an equipment identifier was last seen. The connected Google client requests permitted records through MCP, SiteTrax.io applies account and project access, and the returned observation supports the answer. An action in another system requires an additional defined workflow and permission.

## Choose an integration route

<table id="bkmrk-route-use-it-for-sit"><thead><tr><th>Route</th><th>Use it for</th><th>SiteTrax.io status and next step</th></tr></thead><tbody><tr><td>Google Sheets and My Maps</td><td>Receive operational records in a configured sheet; map available coordinates.</td><td>Documented data-delivery route. Confirm the project destination. My Maps requires reimport to reflect changes.</td></tr><tr><td>Gemini Enterprise custom MCP connection</td><td>Let an enterprise assistant query authorized SiteTrax.io information.</td><td>Google documents this capability. SiteTrax.io end-to-end compatibility has not been validated in this guide; coordinate a pilot.</td></tr><tr><td>Custom Google Cloud agent</td><td>Implement a defined business workflow using SiteTrax.io evidence and other authorized tools.</td><td>Proposed implementation route. Architecture, hosting, billing and support must be scoped.</td></tr><tr><td>Gemini in Gmail or the Gemini consumer app</td><td>Use a particular Google user interface.</td><td>Do not assume a Gemini Enterprise MCP configuration appears in these products. Confirm that exact surface before committing to a workflow.</td></tr></tbody></table>

## 1. Use data in Google Sheets and My Maps

Confirm the Google Sheets destination under your SiteTrax.io project integrations. Once records arrive, use [the existing My Maps guide](https://docs.sitetrax.io/books/google-integrations/page/integrate-google-spreadsheet-with-google-maps) to import coordinates. Map markers describe recorded observations. Reimport the sheet to update the map; a sheet update alone does not refresh it.

## 2. Evaluate Gemini Enterprise access

Google’s [custom MCP data-store guide](https://docs.cloud.google.com/gemini/enterprise/docs/connectors/custom-mcp-server/set-up-custom-mcp-server) documents Streamable HTTP and OAuth setup. That establishes a Google integration path, not a tested SiteTrax.io connection.

For a pilot, have your Google administrator and SiteTrax.io confirm:

- The Gemini Enterprise app, permitted users and required organization policies.
- The endpoint `https://mcp.sitetrax.io/mcp`, OAuth registration and redirect, requested scopes and allowed domains.
- Per-user project access, tool discovery and a read-only test before any notification write permission.

> Using SiteTrax.io, list the projects I can access. Then find the latest observation of the equipment identifier I provide, including its time, project and supporting record.

Compare the answer with the same account in [app.sitetrax.io](https://app.sitetrax.io). Test an inaccessible project and a missing identifier as well as a successful lookup. Publish a customer setup guide only after the actual connection, permissions and supported tools pass validation.

## 3. Build a custom agent on Google Cloud

Google’s [Agent Development Kit supports MCP tools](https://adk.dev/tools-custom/mcp-tools/), and its [Agent Runtime guide](https://docs.cloud.google.com/gemini-enterprise-agent-platform/build/runtime/quickstart-adk) describes hosting ADK agents. A proposed SiteTrax.io implementation uses an agent to call permitted SiteTrax.io tools, apply a defined business process and request an approved downstream action. This does not require describing Gemini as the model that reads asset identifiers from video.

Scope one workflow first. Agree where it runs, who pays for the runtime, how each user or service is authorized, which data reaches Google, what actions require approval and who handles failures. Google Cloud Marketplace procurement is a separate workstream from validating this connection; this guide does not claim a SiteTrax.io listing or Google endorsement.

## Start with a verifiable lookup

[Contact SiteTrax.io](https://www.sitetrax.io/contact) with the Google product you use, one project and one question you need answered. Establish a reliable lookup before expanding to workflows that change business systems.

<small>Provider documentation checked 7 October 2026. SiteTrax.io Google MCP setup remains unvalidated in this review.</small>