---
title: "Connect Google Search Console to Google Cloud Run - APIANT.ai"
description: "When \"New Daily Search Performance\" fires in Google Search Console, your agent runs \"Run Job\" in Google Cloud Run."
canonical: "https://apiant.ai/connect/google-search-console-2-to-google-cloud-run"
---

# Connect Google Search Console to Google Cloud Run

When **New Daily Search Performance** fires in [Google Search Console](https://apiant.ai/connections/google-search-console-2), your agent runs **Run Job** in [Google Cloud Run](https://apiant.ai/connections/google-cloud-run). Describe the whole flow and it is built, tested on every scenario and kept running.

Google Search Console **1** trigger Google Search Console **6** actions Google Cloud Run **6** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Google Search Console and Google Cloud Run to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Google Search Console can start in Google Cloud Run

- When **New Daily Search Performance** in Google Search Console then **Run Job** in Google Cloud Run
- When **New Daily Search Performance** in Google Search Console then **Get Execution** in Google Cloud Run

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Google Search Console and Google Cloud Run

## Triggers and actions 1 trigger · 12 actions

- Trigger

**New Daily Search Performance**

Triggers once per day of search performance data for a property, with that day's clicks, impressions, CTR and position.

- Action

**Get Sitemap**

Returns the details of one submitted sitemap for a property.

- Action

**Inspect URL**

Returns Google's index status for a URL in a property: coverage, last crawl, canonical, mobile usability and rich results.

- Action

**List Sitemaps**

Returns the sitemaps submitted for a property, with their status, errors and warnings.

- Action

**List Sites**

Returns the Search Console properties the connected account can access, with your permission level on each.

- Action

**Search Analytics Query**

Returns search performance rows (clicks, impressions, CTR, position) for a property over a date range, grouped by the dimensions you choose.

- Action

**Submit Sitemap**

Submits (or resubmits) a sitemap for a property so Google crawls it.

- Action

**Get Execution**

Returns a Cloud Run job execution's progress: how many tasks are running, succeeded or failed.

- Action

**Get Service**

Returns a Cloud Run service's URL, latest revision and status.

- Action

**List Jobs**

Returns the Cloud Run jobs in a project, in one region or across all regions.

- Action

**List Revisions**

Returns the revisions of a Cloud Run service.

- Action

**List Services**

Returns the Cloud Run services in a project, in one region or across all regions.

- Action

**Run Job**

Starts a new execution of a Cloud Run job and returns the execution's ID.

## Each app on its own

- [ **Google Search Console** Google Search Console reports how your sites perform in Google Search: queries, clicks, impressions...](https://apiant.ai/connections/google-search-console-2)
- [ **Google Cloud Run** Serverless platform for running containerized services and jobs on Google Cloud.](https://apiant.ai/connections/google-cloud-run)

Reviews

## What our customers say

## More from Google Search Console

- [ **Google Search Console to Upload-Post** Upload-Post is a tool to upload your videos to every social media platform via API with a simple request.](https://apiant.ai/connect/google-search-console-2-to-upload-post)
- [ **Google Search Console to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/google-search-console-2-to-hubspot)
- [ **Google Search Console to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/google-search-console-2-to-salesforce)
- [ **Google Search Console to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/google-search-console-2-to-slack)
- [ **Google Search Console to Google Sheets** Google Sheets](https://apiant.ai/connect/google-search-console-2-to-google-sheets)
- [ **Google Search Console to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/google-search-console-2-to-mailchimp)

## More into Google Cloud Run

- [ **Airtable to Google Cloud Run** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-google-cloud-run)
- [ **SendGrid to Google Cloud Run** SendGrid by Twilio — email delivery and marketing platform.](https://apiant.ai/connect/sendgrid-to-google-cloud-run)
- [ **Outlook to Google Cloud Run** Outlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...](https://apiant.ai/connect/outlook-to-google-cloud-run)
- [ **Postman to Google Cloud Run** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-google-cloud-run)
- [ **HubSpot to Google Cloud Run** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-google-cloud-run)
- [ **Salesforce to Google Cloud Run** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-google-cloud-run)

Questions

## Google Search Console and Google Cloud Run, answered

###

### What can start an automation from Google Search Console?

Any of Google Search Console's 1 trigger in the catalog, including New Daily Search Performance. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Google Cloud Run when something happens in Google Search Console?

Any of Google Cloud Run's 6 actions, including Get Execution, Get Service, List Jobs and List Revisions. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Google Cloud Run to Google Search Console?

Google Cloud Run has no triggers in the catalog today, so automations start in Google Search Console. If you need the other direction, ask: your agent reads Google Cloud Run's API documentation and adds it.

###

### Do I have to build a connector for Google Search Console or Google Cloud Run?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Google Search Console and Google Cloud Run without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
