Integrations / Google

TexAu × Google

OAuth 2.05 actions availableMCP-ready

Used by 1,200+ teams

Connect Google →Talk to sales
Google logo

TexAu integrates with Google. Enrich, sync, and automate every action from one API. Bring it into Claude, Cursor, or any MCP client. Built for sales, RevOps, and growth teams who want a programmable layer on top.

Built for Sales, RevOps, and growth teams running outbound..

5 actionsOAuth 2.0MCP-readyasync-safeREST + Webhooks

What you can build

Three workflows worth shipping with Google.

  • Enrich every new record before it hits Google

    Run the 32-integration waterfall on inbound, write the verified result back.

  • Sync TexAu Tables to Google on a schedule

    Bidirectional sync, conflict resolution, custom field mapping.

  • Trigger Google actions from Claude or your API

    Every action exposed as an MCP tool. Call it from any agent.

The catalog

Every Google action TexAu supports.

Grouped by verb. Each row links to the full input/output schema and a try-it widget.

Other · 5

Google logoGet Google Search Results (Apify)Google logoGet Google Top Search Result (Apify)Google logoGet Google Maps Places Using Search Url (Apify)Google logoGet Google Maps Reviews (Apify)Google logoGet Google Maps Places Using Search Keyword (Apify)

The trace

How a Google workflow runs.

Google → TexAu enrichment → Google writeback. One trace, every step observable.

Google logoGoogle
TexAu enrichment
Google logoGoogle

Auth & setup

Connect Google in four steps.

Screenshots coming soon. The flow below is the live four-step setup.
  1. 1

    Open the Google app in TexAu

    Studio → Connections → Google.

  2. 2

    Click Connect, we redirect you to Google

    OAuth 2.0 consent screen. You pick the scopes.

  3. 3

    Authorize TexAu

    Google hands us a refresh token. We never see your password.

  4. 4

    Run your first action

    Pick any action from the catalog above and try it live.

MCP for Google

Bring Google into Claude, Cursor, or any MCP client.

Drop this into your config. Every action above becomes a tool the model can call.

claude_desktop_config.json
{
  "mcpServers": {
    "texau-google": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": {
        "TEXAU_API_KEY": "...",
        "TEXAU_PLATFORM": "google"
      },
      "tools": [
        "google-search-scraper-sync",
        "google-search-scraper-top-result",
        "google-maps-places-scraper-sync-using-url",
        "google-maps-reviews-scraper-sync",
        "google-maps-places-scraper-sync"
      ]
    }
  }
}

Compared

Where TexAu wins vs native Google automation.

Enrichment depth

Native: one provider. TexAu: 32-integration waterfall with attribution.

Branching logic

Native: linear. TexAu: real conditionals, retries, async-safe steps.

AI surface

Native: none. TexAu: every action is also an MCP tool.

Migration

From Zapier or manual scripts to TexAu.

Most Google teams land on TexAu after they hit the ceiling of Zapier or manual scripts. The pattern is the same: a workflow worked for the first 10 contacts, then it broke at 1,000. Steps timed out. Branching turned into a Frankenstein. Enrichment was always one provider deep, so half the rows came back empty.

TexAu replaces the brittle middle. The 32-integration waterfall fills the rows that Zapier or manual scripts left empty. Async-safe steps mean a slow LinkedIn fetch does not block the whole run. Branching is real branching, not nested filters. And every action you build for Google is also an MCP tool. Claude can call it, your API can call it, your Studio operator can run it from a Table.

We import existing workflows. We do not ask you to rebuild from scratch. Most teams are running the same automations on TexAu within a week, with deeper enrichment and observable traces from day one.

Connect Google in Studio →

Free to start. No credit card. Every action above runs in your first session.

Start free →Talk to sales