Integration
Connect Google Ads to openSenseMap
When New Campaign fires in Google Ads, your agent runs Find measurements by phenomenon in openSenseMap. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Google Ads and openSenseMap to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Google Ads can start in openSenseMap
When New Campaign in Google Ads
then Find measurements by phenomenon in openSenseMap
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 Ads and openSenseMap
Triggers and actions 1 trigger · 17 actions
- New Campaign
Triggers when a new campaign is created in a Google Ads account.
- Create Customer List
Creates a Customer Match audience list in a Google Ads account.
- Find Campaign
Finds Google Ads campaigns whose name exactly matches the name given.
- Get Campaign
Returns one Google Ads campaign by its id, with its status, type, dates and daily budget.
- Get Campaign Performance Report
Returns cost, impressions, clicks and conversions for each campaign in a Google Ads account, one row per campaign per day, for a date range.
- List Accessible Customers
Returns the Google Ads customer account ids the connected user can access directly.
- List Campaigns
Returns every campaign in a Google Ads account that has not been removed, with status, type, dates and daily budget.
- List Customer Lists
Returns the Customer Match audience lists in a Google Ads account.
- Set Campaign Status
Pauses or enables a Google Ads campaign.
- Update Campaign Budget
Changes the daily amount of a Google Ads campaign budget.
- Find measurements by phenomenon
Fetch the latest measurements for all sensors measuring a given phenomenon/grouptag, as JSON or CSV.
- Find senseBoxes near location
Search senseBoxes near a given coordinate/bounding box and phenomenon.
- Get 10000 latest measurements for sensor
Fetch up to the 10000 latest raw measurements for one sensor, with optional from-date/to-date filters.
- Get database statistics
Fetch overview statistics about the openSenseMap database (box count, sensor count, measurement count).
- Get latest measurements of senseBox
Fetch the latest measurements of all sensors for a given senseBox.
- Get latest measurements of sensor
Fetch the latest measurement value for one specific sensor of a senseBox.
- Get senseBox
Fetch details for one senseBox station by its ID.
- List senseBoxes
List all senseBox stations, optionally filtered by bounding box/phenomenon/exposure.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Google Ads
Google Ads to VercelVercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.
Google Ads to TwentyTwenty is a modern Open-Source CRM platform.
Google Ads to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google Ads to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Ads to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Ads to Google SheetsGoogle Sheets
More into openSenseMap
Gmail to openSenseMapGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to openSenseMapGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Google Ads and openSenseMap, answered
What can start an automation from Google Ads?
Any of Google Ads's 1 trigger in the catalog, including New Campaign. Describe the moment in plain language and your agent picks the right one.
What can your agent do in openSenseMap when something happens in Google Ads?
Any of openSenseMap's 8 actions, including Find measurements by phenomenon, Find senseBoxes near location, Get 10000 latest measurements for sensor and Get database statistics. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from openSenseMap to Google Ads?
openSenseMap has no triggers in the catalog today, so automations start in Google Ads. If you need the other direction, ask: your agent reads openSenseMap's API documentation and adds it.
Do I have to build a connector for Google Ads or openSenseMap?
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.
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.