Integration
Connect Grist and Wachete
When New or Updated Record fires in Grist, your agent runs Create monitor in Wachete, or New notification for monitor in Wachete to Create or Update Record in Grist. 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 Grist and Wachete 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 Grist and Wachete can do together
From Grist to Wachete
When New or Updated Record in Grist
then Create monitor in Wachete
From Wachete to Grist
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 Grist and Wachete
Triggers and actions 6 triggers · 28 actions
- New or Updated Record
Triggered when a row in a Grist table is created or updated.
- New or Updated Record (Instant)
Triggers when a Record is updated, or a new Record is added.
- New Record
Triggered when a new row is added to a Grist table.
- New Record (Instant)
Triggers when a new Record is created
- Add Column
Adds a column to a table in a Grist document.
- Add Table
Creates a new table in a Grist document, optionally with a starting set of columns.
- Create Document
Creates a new document in a Grist workspace and returns its document ID.
- Create or Update Record
Adds a row to a Grist table, or updates the existing row when the match column already holds the match value. Returns the row ID.
- Create Record
Adds a new row to a Grist table and returns its row ID.
- Create Workspace
Creates a new workspace in a Grist organization and returns its ID.
- Delete Document
Deletes a Grist document permanently.
- Delete Records
Deletes one or more rows from a Grist table by row ID.
- Delete Workspace
Deletes a Grist workspace along with every document inside it.
- Find Record
Searches a Grist table for a row whose column holds a given value and returns that row's ID and column values.
- Get Document
Returns the details of one Grist document — its name, web address, workspace, and organization.
- Get Org
Returns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level.
- Get Workspace
Returns the details of one Grist workspace, including the documents it contains.
- List Columns
Returns the columns of a Grist table, with each column's ID, label, and type.
- List Orgs
Returns every Grist organization (team site) this connection can reach.
- List Tables
Returns the tables in a Grist document.
- List Workspaces
Returns the workspaces in a Grist organization, each with the documents it contains.
- Run SQL Query
Runs a read-only SELECT statement against a Grist document and returns the rows.
- Update Document
Renames a Grist document or changes whether it is pinned. Anything left blank stays as it is.
- Update Record
Changes the column values of one row in a Grist table. Columns left blank keep their current values.
- Update Workspace
Renames a Grist workspace.
- 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 Grist
Grist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Grist to ClickhouseColumn-oriented database for real-time analytical SQL queries at petabyte scale.
Grist to Mistral AIMistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...
Grist to OpusClipOpusClip is a AI video tool that turns long videos into viral shorts with captions and transcripts.
Grist to PostmanPostman is a platform for building and testing APIs.
Grist to RuneScapeThe RuneScape Wiki API exposes data for RuneScape and Old School RuneScape.
More into Wachete
HubSpot to WacheteHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to WacheteSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to WacheteMailchimp marketing automation and email platform.
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
Grist and Wachete, answered
What can start an automation from Grist?
Any of Grist's 4 triggers in the catalog, including New or Updated Record, New or Updated Record (Instant), New Record and New Record (Instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wachete when something happens in Grist?
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 Grist?
Yes. When something happens in Wachete, your agent can act in Grist too. This page covers both directions: Wachete's triggers and Grist's actions are listed here as well.
Do I have to build a connector for Grist 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.
Can my AI client use Grist and Wachete 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.