Integration
Connect Grist and SQL Server
When New or Updated Record fires in Grist, your agent runs Add Row in SQL Server, or New or Updated Row in SQL Server 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 SQL Server 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 SQL Server can do together
From Grist to SQL Server
When New or Updated Record in Grist
then Add Row in SQL Server
When New Record in Grist
then Update Row in SQL Server
From SQL Server to Grist
When New or Updated Row in SQL Server
then Create or Update Record in Grist
When New Row in SQL Server
then Create Record in 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 SQL Server
Triggers and actions 8 triggers · 28 actions
Trigger
New or Updated RecordTriggered when a row in a Grist table is created or updated.
Trigger
New or Updated Record (Instant)Triggers when a Record is updated, or a new Record is added.
Trigger
New RecordTriggered when a new row is added to a Grist table.
Trigger
New Record (Instant)Triggers when a new Record is created
Action
Add ColumnAdds a column to a table in a Grist document.
Action
Add TableCreates a new table in a Grist document, optionally with a starting set of columns.
Action
Create DocumentCreates a new document in a Grist workspace and returns its document ID.
Action
Create or Update RecordAdds a row to a Grist table, or updates the existing row when the match column already holds the match value. Returns the row ID.
Action
Create RecordAdds a new row to a Grist table and returns its row ID.
Action
Create WorkspaceCreates a new workspace in a Grist organization and returns its ID.
Action
Delete DocumentDeletes a Grist document permanently.
Action
Delete RecordsDeletes one or more rows from a Grist table by row ID.
Action
Delete WorkspaceDeletes a Grist workspace along with every document inside it.
Action
Find RecordSearches a Grist table for a row whose column holds a given value and returns that row's ID and column values.
Action
Get DocumentReturns the details of one Grist document — its name, web address, workspace, and organization.
Action
Get OrgReturns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level.
Action
Get WorkspaceReturns the details of one Grist workspace, including the documents it contains.
Action
List ColumnsReturns the columns of a Grist table, with each column's ID, label, and type.
Action
List OrgsReturns every Grist organization (team site) this connection can reach.
Action
List TablesReturns the tables in a Grist document.
Action
List WorkspacesReturns the workspaces in a Grist organization, each with the documents it contains.
Action
Run SQL QueryRuns a read-only SELECT statement against a Grist document and returns the rows.
Action
Update DocumentRenames a Grist document or changes whether it is pinned. Anything left blank stays as it is.
Action
Update RecordChanges the column values of one row in a Grist table. Columns left blank keep their current values.
Action
Update WorkspaceRenames a Grist workspace.
Trigger
New or Updated RowTriggers when a new row is added or modified.
Trigger
New or Updated Row (Custom Query)Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.
Trigger
New RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected SQL Server database.
Action
Add RowAdd one row to a table on the connected SQL Server database.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFind the first row in a table whose chosen column matches a value.
Action
Find Rows via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns every row it matches.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
Action
Run Custom StatementRuns a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
Action
Update RowChange column values on every row of a table whose chosen column matches a value.
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 SQL Server
HubSpot to SQL ServerHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to SQL ServerSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to SQL ServerMailchimp marketing automation and email platform.
Shopify to SQL ServerShopify is a commerce platform for online stores and retail point-of-sale.
QuickBooks Online to SQL ServerQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to SQL ServerPipedrive is a sales CRM and pipeline management tool.
Questions
Grist and SQL Server, 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 SQL Server when something happens in Grist?
Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SQL Server to Grist?
Yes. When something happens in SQL Server, your agent can act in Grist too. This page covers both directions: SQL Server's triggers and Grist's actions are listed here as well.
Do I have to build a connector for Grist or SQL Server?
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 SQL Server 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.