Integration
Connect Google Merchant Center to Qase
When New or Updated Product fires in Google Merchant Center, your agent runs Add project in Qase. 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 Qase 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 Qase
When New or Updated Product in Google Merchant Center
then Add project in Qase
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 Qase
Triggers and actions 1 trigger · 34 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.
- Add defect
Adds a new defect to a Qase project.
- Add milestone
Creates a milestone in a Qase project.
- Add project
Create a new project.
- Add run
Create a new test run in a project.
- Add test case
Create a new test case in a project.
- Add test run result
Create a result for a test run.
- Complete run
Mark a specific test run as completed.
- Delete project
Delete a project by code.
- Delete run
Delete a test run by id.
- Delete test case
Delete a test case by id.
- Find entities by QQL
Searches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.
- Get defect
Get a specific defect by id.
- Get project
Get a project by its code.
- Get run
Retrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.
- Get test case
Get a specific test case by id.
- Get test run result
Get a test run result by hash code.
- List defects
Returns all defects in a Qase project, optionally filtered by status.
- List milestones
Get all milestones in a project.
- List projects
Lists every project available to the connected Qase account.
- List runs
Get all test runs in a project.
- List test cases
Get all test cases in a project.
- List test run results
Get all results for a project's test runs.
- Resolve defect
Marks a specific defect in a Qase project as resolved.
- Update defect
Update an existing defect.
- Update run
Update a specific test run.
- Update test case
Updates an existing test case in a Qase project. Only the fields you fill in are changed.
- Update test run result
Update a test run result.
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
More into Qase
Gmail to QaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Google Merchant Center and Qase, 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 Qase when something happens in Google Merchant Center?
Any of Qase's 27 actions, including Update defect, Update run, Update test case and Update test run result. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qase to Google Merchant Center?
Qase has no triggers in the catalog today, so automations start in Google Merchant Center. If you need the other direction, ask: your agent reads Qase's API documentation and adds it.
Do I have to build a connector for Google Merchant Center or Qase?
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 Qase 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.