# Grist integrations: records, tables and columns

> Add records to a table, add tables to a document and add columns to a table in Grist, and start a workflow when Grist sends “Record added”.

**Canonical page:** https://tray.ai/connectors/grist-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Grist is a spreadsheet-database hybrid where teams build relational tables with formulas, forms and access rules, hosted or self-managed. Tray.ai connects to Grist through the HTTP Connector, so your workflows can call the Grist API alongside the rest of your stack.

## Use cases

### Records

Read, create, and delete records in Grist from any Tray.ai workflow. The Grist API covers calls such as fetch records from a table and add records to a table.

- Fetch records from a table
- Add records to a table
- Modify records

### Tables

Read and create tables in Grist from any Tray.ai workflow. The Grist API covers calls such as list tables in a document and add tables to a document.

- List tables in a document
- Add tables to a document
- Modify tables

### Columns

Read and create columns in Grist from any Tray.ai workflow. The Grist API covers calls such as list columns in a table and add columns to a table.

- List columns in a table
- Add columns to a table
- Modify columns

### Documents

Create and delete documents in Grist from any Tray.ai workflow. The Grist API covers calls such as create a document and describe a document.

- Create a document
- Describe a document
- Copy a document

### Workspaces

Read, create, and delete workspaces in Grist from any Tray.ai workflow. The Grist API covers calls such as list workspaces and create a workspace.

- List workspaces
- Create a workspace
- Delete a workspace

### Webhooks

Read, create, and delete webhooks in Grist from any Tray.ai workflow. The Grist API covers calls such as list webhooks and create webhooks.

- List webhooks
- Create webhooks
- Modify a webhook

## Challenges Tray.ai solves

### Keeping Grist credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Grist credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Grist API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Grist API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Grist?

Yes. Tray.ai connects to Grist through the HTTP Connector, which calls the Grist API directly. Any call the Grist API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Grist?

The Grist API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Grist connector?

Grist runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Grist connector from the Grist API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/