--- title: "Connect Google Search Console to EMnify - APIANT.ai" description: "When \"New Daily Search Performance\" fires in Google Search Console, your agent runs \"Create a Device\" in EMnify." canonical: "https://apiant.ai/connect/google-search-console-2-to-emnify" --- # Connect Google Search Console to EMnify When **New Daily Search Performance** fires in [Google Search Console](https://apiant.ai/connections/google-search-console-2), your agent runs **Create a Device** in [EMnify](https://apiant.ai/connections/emnify). 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 EMnify **7** 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 EMnify 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 EMnify - When **New Daily Search Performance** in Google Search Console then **Create a Device** in EMnify - When **New Daily Search Performance** in Google Search Console then **Disable a Device** in EMnify 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 EMnify ## Triggers and actions 1 trigger · 13 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 **Create a Device** Creates a device and assigns the SIM by ICCID. - Action **Delete a Device** Deletes a device (endpoint) and all its child entities. Devices with an assigned SIM cannot be deleted. - Action **Disable a Device** Disables a device (endpoint) in EMnify by setting its status to Disabled. The SIM stays active and may still be charged; suspend the SIM separately to stop charges. - Action **Enable a Device** Sets an EMnify device (endpoint) status to Enabled so it can use network services. EMnify still charges for activated SIMs regardless of device status. - Action **Find Devices by criteria** Returns the devices (endpoints) that match the specified filter criteria, such as name, ICCID, IMEI, tags or status. - Action **Get a Device** Retrieve a single endpoint (device) by ID. - Action **Reconfigure a Device** Reconfigure and activate a device by ICCID. ## 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) - [ **EMnify** EMnify is a cloud communication platform for IoT that transforms complex global cellular connectivity into...](https://apiant.ai/connections/emnify) 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 EMnify - [ **HubSpot to EMnify** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-emnify) - [ **Salesforce to EMnify** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-emnify) - [ **Slack to EMnify** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-emnify) - [ **Google Sheets to EMnify** Google Sheets](https://apiant.ai/connect/google-sheets-to-emnify) - [ **Gmail to EMnify** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-emnify) - [ **Google Calendar to EMnify** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-emnify) Questions ## Google Search Console and EMnify, 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 EMnify when something happens in Google Search Console? Any of EMnify's 7 actions, including Create a Device, Disable a Device, Enable a Device and Find Devices by criteria. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from EMnify to Google Search Console? EMnify has no triggers in the catalog today, so automations start in Google Search Console. If you need the other direction, ask: your agent reads EMnify's API documentation and adds it. ### ### Do I have to build a connector for Google Search Console or EMnify? 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 EMnify 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.