Integration
Connect Google Forms and Wachete
When New Form Response fires in Google Forms, your agent runs Create monitor in Wachete, or New notification for monitor in Wachete to Add Question in Google Forms. 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 Forms and Wachete 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 Forms and Wachete can do together
From Google Forms to Wachete
When New Form Response in Google Forms
then Create monitor in Wachete
From Wachete to Google Forms
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 Forms and Wachete
Triggers and actions 4 triggers · 13 actions
- New Form Response
Triggers when a new form response is received.
- New or Updated Form Response
Triggers when a form response is added or modified.
- Add Question
Adds a question (short answer, paragraph, multiple choice, checkboxes or drop-down) to an existing form.
- Create Form
Creates a new, empty Google Form with a title. Add questions with Add Question.
- Get Form
Returns a form's title, description, responder link and questions.
- Get Form Response
Returns one response submitted to a form, with its answers.
- List Form Responses
Returns the responses submitted to a form, with each response's answers.
- Update Form Info
Updates a form's title and/or description; a field left blank is kept.
- Any new notification
Fires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
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 Forms
Google Forms to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google Forms to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Forms to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Forms to Google SheetsGoogle Sheets
Google Forms to MailchimpMailchimp marketing automation and email platform.
Google Forms to StripeStripe is a payment processing platform for online businesses.
More into Wachete
Shopify to WacheteShopify is a commerce platform for online stores and retail point-of-sale.
QuickBooks Online to WacheteQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to WachetePipedrive is a sales CRM and pipeline management tool.
Questions
Google Forms and Wachete, answered
What can start an automation from Google Forms?
Any of Google Forms's 2 triggers in the catalog, including New Form Response and New or Updated Form Response. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in Google Forms?
Any of Wachete's 7 actions, including Create monitor, Update monitor, Get monitor and Get monitor data. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wachete to Google Forms?
Yes. When something happens in Wachete, your agent can act in Google Forms too. This page covers both directions: Wachete's triggers and Google Forms's actions are listed here as well.
Do I have to build a connector for Google Forms or Wachete?
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.