Integration
Connect Google Merchant Center to Avoma
When New or Updated Product fires in Google Merchant Center, your agent runs Update call in Avoma. 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 Merchant Center and Avoma to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 Merchant Center can start in Avoma
When New or Updated Product in Google Merchant Center
then Update call in Avoma
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 Merchant Center and Avoma
Triggers and actions 1 trigger · 19 actions
- New or Updated Product
Triggers when a product is added to or changed in a Merchant Center account. Google takes about 5 minutes to process a product change, so it fires after that delay.
- Delete Product Input
Deletes a product input from a Merchant Center data source.
- Get Product
Returns one product from a Merchant Center account, including its approval status and issues. A newly added or changed product can take about 5 minutes to appear here.
- Insert Product Input
Creates or replaces a product in a Merchant Center data source.
- List Accounts
Returns the Merchant Center accounts the connected Google login can access.
- List Data Sources
Returns the data sources (product feeds) configured in a Merchant Center account.
- List Products
Returns the products in a Merchant Center account. A newly added or changed product can take about 5 minutes to appear here.
- Update Product Input
Updates selected attributes of an existing product input in a Merchant Center data source.
- Get call
Returns a single Avoma call by its external ID, including its CRM links, recording URL, processing state and linked meeting.
- Get meeting
Returns a single Avoma meeting by its UUID, including its attendees, schedule, state, and recording and transcription details.
- Get meeting insights
Returns the AI notes, keyword occurrences, popular keywords and speakers for a completed Avoma meeting.
- Get recording
Returns the signed audio and video download links for the recording of an Avoma meeting. If the video is still being processed, returns a message instead of the links.
- Get transcription
Returns the transcript of a meeting's recording, including the speakers, the timed transcript text and a link to the VTT file.
- List calls
Returns the calls in your Avoma organization that started within a date range, optionally narrowed to inbound or outbound calls.
- List meetings
Returns the meetings in your Avoma organization that started within a date range, optionally filtered by attendee, CRM record, recording length or meeting type.
- List notes
Returns the AI-generated notes for meetings in a date range, optionally narrowed to one meeting or custom category.
- List scorecard evaluations
Returns completed scorecard evaluations for meetings, optionally narrowed by date range, scorecard template, meeting or evaluated user.
- List users
Returns the users in your Avoma organization, including each user's name, email, role, teams and status.
- Update call
Updates an existing call's details in Avoma, such as its subject, participant names, meeting purpose and outcome, or linked CRM records, and returns the updated call.
- Upload Audio Call
Creates a call in Avoma from a publicly reachable audio recording. Avoma downloads the recording and processes it into a transcript and notes, or uses a transcript you supply.
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 Merchant Center
Google Merchant Center to Google Tag ManagerTag management system for deploying and configuring website/app tracking codes, tags, and triggers without...
Google Merchant Center to SquareSquare is a commerce platform for payments, point of sale, orders, customers, catalog, and invoices.
Google Merchant Center to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google Merchant Center to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Merchant Center to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Merchant Center to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
More into Avoma
Gmail to AvomaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AvomaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Google Merchant Center and Avoma, answered
What can start an automation from Google Merchant Center?
Any of Google Merchant Center's 1 trigger in the catalog, including New or Updated Product. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Avoma when something happens in Google Merchant Center?
Any of Avoma's 12 actions, including Update call, Upload Audio Call, Get call and Get meeting. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Avoma to Google Merchant Center?
Avoma has no triggers in the catalog today, so automations start in Google Merchant Center. If you need the other direction, ask: your agent reads Avoma's API documentation and adds it.
Do I have to build a connector for Google Merchant Center or Avoma?
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 Merchant Center and Avoma 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.