Skip to content

Start building

Integration · Databases

AI agents for Grist

Find Grist documents, list their tables and columns, fetch records with filters, run read-only SQL over a document, and add, update, upsert and delete records, on Grist Cloud.

Actions
9
Read
5
Write
4

Actions

What your agents can do in Grist

Find Grist documents, list their tables and columns, fetch records with filters, run read-only SQL over a document, and add, update, upsert and delete records, on Grist Cloud (personal or team site) or your own Grist server, with your API key.

Read 5

Look things up. Nothing changes.

  • List workspaces and documents

    Lists the site's workspaces with their documents, to find a document's ID.

  • List tables

    Lists a document's tables.

  • List columns

    Lists a table's columns.

  • Fetch records

    Fetches records of a table, optionally only those whose columns hold one of the given values, sorted and limited.

  • Run SQL

    Runs one read-only SQLite SELECT (WITH allowed, no closing semicolon) over a document, whose tables are named by their table IDs, like SELECT Name, Total FROM Orders WHERE Total > ?

Write 4

Create, change or send.

  • Add records

    Adds records to a table.

  • Update records

    Changes some columns of records by row ID; columns left out keep their values.

  • Add or update records

    For each entry, finds the record whose columns match require (like {"Email": "ada@example.com"}) and sets fields on it, or adds a record with both when none matches.

  • Delete recordsDeletes data

    Deletes records by row ID, for good (the document's history keeps them).

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Grist account.

What you enter

  • API key

Settings

  • Grist address

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Grist data

    Ask a question in plain words. The agent can list workspaces and documents, list tables or list columns in Grist, then answers with what it found.

  • 02

    Let an agent update Grist

    Have the agent add records or update records in Grist as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Grist and Slack: it can list workspaces and documents in Grist and post a summary to a Slack channel in the same run.

FAQ

Grist and MyDeepAgents

Can MyDeepAgents connect to Grist?

Yes. The Grist connector has 9 actions: 5 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Grist?

Paste an API key from your Grist account. You'll need: API key. The connection also asks for: Grist address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Grist without asking?

Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.

Can I use Grist in workflows as well as agents?

Yes. Every Grist action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Grist to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.