Google connector preview

Build Google-connected apps from a prompt.

WandGx Connect lets generated apps declare Google service needs as inspectable connector manifests, scope summaries, backend endpoint lists, status panels, and repair prompts.

WandGx never exposes OAuth tokens to generated frontend code. Generated apps call WandGx connector endpoints; credentials stay encrypted server-side.

Supported Google services

Generated apps use least-privilege scopes for the services they request. Gemini Enterprise remains a future module behind a feature flag.

Gmail

Search and read messages, draft or send reviewed email, and apply labels.

Google Calendar

Read events, check availability, and create or update events.

Google Drive

List or search files and folders, download selected files, and store generated artifacts.

Google Sheets

Read and write ranges, append rows, query records, and use Sheets as a lightweight app backend.

Google Docs

Generate structured documents from app data and save them to Drive.

Google Slides

Generate or update decks from briefs, reports, and app workflows.

Google Maps Platform

Geocode addresses, calculate distances, show maps, and fetch place details.

BigQuery

Run bounded read-only analytics queries for generated dashboards.

Generated app contract

What every connector-backed app includes

The differentiator is not just API access. WandGx keeps the connector contract inspectable, repairable, and safe to hand off.

Connector manifest with services, actions, scopes, and backend endpoints.
Visible permission and scope summary before a connection is linked.
Connection status panel for connected, reconnect, missing-scope, rate-limited, owner-disabled, and demo states.
Backend requests under WandGx connector endpoints instead of direct browser calls to Google APIs.
Mock data mode when a Google connection is not active.
Handoff evidence listing sources, scopes, backend endpoints, audit and usage evidence paths, tests run, and known limitations.
Security boundary

Backend-only credentials

Generated apps never receive Google refresh tokens, OAuth client secrets, service-account keys, Maps server keys, or raw WandGx connector credentials. If a connection is absent or broken, the app must show demo data, reconnect copy, or a structured repair state.

Google connector generation is in preview. Live Google OAuth callback checks and real generated-app E2E checks must pass before public copy claims broadly available Google account linking.

Example prompts
Build a booking page that checks my Google Calendar availability and creates events.
Build a CRM backed by this Google Sheet and show recent Gmail threads per contact.
Build a client portal that lists files from this Google Drive folder.
Generate a proposal Doc and kickoff Slides deck when a new client is added to Sheets.
Build a dashboard from BigQuery metrics and email a weekly Gmail summary.

Troubleshooting

Pop-up blocked

Restart authorization from the Google connector dashboard and allow the Google authorization window.

Missing scope

Reconnect the service and approve the scope listed in the generated app status panel.

Expired authorization

Use reconnect when Google revokes or expires permissions. WandGx refreshes tokens server-side when possible.

Wrong Google account

Disconnect the connection, then reconnect with the intended Google account.

Shared Drive or calendar permissions

Confirm the connected account can access the target folder, file, or calendar.

BigQuery dataset access

Confirm dataset permissions and the backend BigQuery project allowlist before running dashboard queries.