Integration
Connect Grist to NameAPI
When New or Updated Record fires in Grist, your agent runs Detect contact risk in NameAPI. 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 NameAPI 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 Grist can start in NameAPI
When New or Updated Record in Grist
then Detect contact risk in NameAPI
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 NameAPI
Triggers and actions 4 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.
- Detect contact risk
Risk Detector: scores a person/email/address record for fake or risky data.
- Detect disposable email address
Disposable Email Address Detector: checks whether an email is disposable.
- Format person name
Name Formatter: formats a person name (e.g. salutation/full name) per locale.
- Genderize person name
Name Genderizer: infers gender from a person name.
- Match person names
Name Matcher: compares two person names and returns a match type/confidence.
- Parse email name
Email Name Parser: extracts a person name from an email address.
- Parse person name
Name Parser: splits a full name into components (given/family names, title, gender).
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 PostmanPostman is a platform for building and testing APIs.
Grist to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Grist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Grist to Google SheetsGoogle Sheets
Grist to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into NameAPI
Slack to NameAPISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Calendar to NameAPIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Grist and NameAPI, 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 NameAPI when something happens in Grist?
Any of NameAPI's 7 actions, including Detect contact risk, Detect disposable email address, Format person name and Genderize person name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from NameAPI to Grist?
NameAPI has no triggers in the catalog today, so automations start in Grist. If you need the other direction, ask: your agent reads NameAPI's API documentation and adds it.
Do I have to build a connector for Grist or NameAPI?
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.