Sanaf AI
Start free
Productivity

Grist, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Grist account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Productivity
  • Connects with a key
  • 32 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Grist is

Grist is a relational spreadsheet platform that combines the flexibility of a spreadsheet with the robustness of a database, allowing users to create custom applications tailored to their data needs.

You paste in a key from your own Grist account. It is kept encrypted, and you can withdraw it from inside Grist whenever you like.

How a run works

One message in, the work done in Grist.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Grist. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Grist account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

32 tools it already has

What it can do in Grist

These are the ready-made tools your AI employee already has in Grist. It is not limited to them, but it never has to be taught these.

  • Add RecordsTool to add records to a specified table in a Grist document. Use after confirming doc and table IDs.
  • Create DocumentTool to create a document in a workspace. Use when you need to add a new document programmatically after selecting a workspace.
  • Create Document WebhookTool to create a new webhook for a specified document. Use when you need to register webhook endpoints for document events in Grist. Run after confirming document ID.
  • Create SCIM UserTool to create a new SCIM user. Use when provisioning new user accounts via SCIM. Run after gathering all required user details.
  • Create TableTool to create tables in a document. Use after confirming the document ID. Creates one or more tables with specified columns in the given document.
  • Delete AttachmentTool to delete a specified attachment from a Grist document. Use when you need to remove a file by providing its document and attachment IDs.
  • Delete ColumnTool to delete a column from a Grist document table. Use after confirming document, table, and column IDs.
  • Delete Grist Table RecordsTool to delete records from a specified Grist table. Use when you need to remove specific rows by their IDs. Use after confirming the row IDs exist.
  • Delete SCIM UserTool to delete a specified user via SCIM. Use after confirming the user's SCIM user ID exists.
  • Delete WebhookTool to delete a webhook from a Grist document. Use when you need to remove a specific webhook after confirming its ID.
  • Download All Attachments ArchiveTool to download all attachments from a Grist document as a .zip or .tar archive. Use after ensuring attachments exist in the specified document.
  • Download AttachmentTool to download the binary data of an attachment. Use when you have the document ID and attachment ID and need the raw file content.
  • Download Grist Attachment ContentTool to download the raw bytes of an attachment. Use when you need to retrieve the binary data of a specific Grist document attachment after confirming the document and attachment
  • Fetch Column MetadataTool to fetch metadata for a specific column in a Grist document table. Use when you need to inspect column properties before data operations.
  • Fetch Document MetadataTool to fetch metadata for a specified Grist document. Use after obtaining the document ID.
  • Fetch Table MetadataTool to retrieve metadata for a specified table in a Grist document. Use when you need to inspect table schema details before data operations.
  • Get Org AccessTool to fetch org access details. Use when you need to retrieve numeric user IDs for actions like SCIM user deletion when SCIM API is disabled.
  • Get UsersTool to retrieve a list of users via SCIM v2. Use when you need to page through and filter enterprise users in Grist.
  • List AttachmentsTool to list all attachments in a Grist document. Use after confirming the document ID to retrieve attachment metadata.
  • List ColumnsTool to list all columns in a specified Grist table. Use after selecting the document and table to inspect column metadata.
  • List OrganizationsTool to list all organizations accessible to the authenticated user. Use when you need to select a Grist organization for subsequent operations.
  • List RecordsTool to retrieve records from a specified table within a Grist document. Use when you need to fetch rows by applying optional filters, sorting, limits, or hidden columns. Example:
  • List TablesTool to list all tables within a specified document. Use after obtaining the document ID to retrieve its tables.
  • List WebhooksTool to list webhooks configured for a document. Use when you need to retrieve all webhooks for a document after obtaining its ID.
  • List WorkspacesTool to list all workspaces and documents accessible to the authenticated user on the current site. Use when you need to select a workspace or document for subsequent operations.
  • Run SQL QueryTool to execute a read-only SQL SELECT query on a Grist document. Use after confirming the document ID and preparing a valid SQL SELECT statement.
  • Update Column MetadataTool to update metadata for one or more columns in a Grist document table. Use after confirming document and table IDs. Example: change label or type of columns.
  • Update Document MetadataTool to update metadata for a specified Grist document. Use when you need to rename or pin/unpin a document after obtaining its ID.
  • Update RecordsTool to update records in a specified table within a document. Use after fetching record IDs.
  • Update Table MetadataTool to update metadata for a specified table. Use after confirming document and table IDs to modify properties such as onDemand or visibility.
  • Update WebhookTool to update an existing webhook for a specified document. Use when you need to modify webhook settings after confirming document and webhook IDs.
  • Upload AttachmentTool to upload one or more attachments to a Grist document. Use when you need to add files to a document after preparing file data.
Access, and who is in charge of it

You stay the boss of your Grist account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Grist account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Grist is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Grist and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Grist

Can an AI employee really work inside Grist?
Yes. It signs in to your own Grist account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Grist?
No. Nothing moves and nothing is replaced. Your records stay in Grist, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Grist account?
You paste in a key from your own Grist account. It is kept encrypted, and you can withdraw it from inside Grist whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Grist?
It has 32 ready-made tools in Grist today, among them Add Records, Create Document and Create Document Webhook. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Grist and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Grist and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Grist?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Grist is written down with what it did and when.