Resources · Make integration

Grist Make integrationAutomate Grist with Make.

Your Grist tables can feed the rest of your tools without copy and paste. The Grist Make integration gives you 31 modules: 2 triggers, 21 actions and 8 searches. This guide is for ops people who know Grist but not Make, and it walks you from the API key to a live scenario.

Try the Grist integration on Make See the 31 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Grist Make integration do for you?

The Grist Make integration links your Grist account to Make, a visual tool where you build a scenario: an automation made of bricks called modules. Each module does one thing in Grist, like adding rows, exporting a table or changing who can open a document, and Make runs the chain for you.

Rows that fill themselves. A web form, a CRM or a spreadsheet elsewhere sends its data, and Add Records to a Table writes it into the right Grist table. When the record already exists, Update Records of a Table changes it instead of creating a duplicate.

Exports that leave on their own. Watch Documents spots a document that was created or updated, then Get a Document Table as CSV File or Get a Document as Excel File produces a file you can drop in a shared drive or attach to an email for the accounting team.

Access that follows your org chart. When a contractor starts or leaves, Update a Document Access and Update a Workspace Access change permissions, and List a Document Users tells you who still has the keys.

What Make does not do here: neither Grist trigger is instant, and no trigger watches individual rows. Make checks documents and workspaces on the scenario's schedule. For anything the listed modules skip, Make an API Call reaches the rest of the Grist API. Grist also has an n8n node, covered in the Grist n8n integration guide, and the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect Grist to Make?

01
Create an API key in Grist
In Grist, click your profile picture or initial at the top right, open Profile Settings, scroll to the API section and click Create. Copy the key it shows. You need an active Grist account for this.
02
Add a Grist module in Make
Open your scenario in Make, add any Grist module and click Create a connection. A connection is your Grist account linked to Make once, then reused by every Grist module you add later.
03
Paste the key and save
Give the connection a clear name in Connection name if you like (it is optional), paste the API key you copied, and confirm. Make can now list your documents and tables in the module fields.

First scenario

Your first scenario: export a Grist table whenever a document changes

GoalWhen a document is created or updated in Grist, Make pulls one of its tables out as a CSV file.

01
Start a new scenario
Go to the Scenarios page in Make, create a new scenario and click the big +. That empty circle is where your first module goes.
02
Add Watch Documents
Search for Grist, pick Watch Documents and select the connection you just made (or click Create a connection if you skipped that part).
03
Add the CSV export
Click the + on the right of the trigger and choose Get a Document Table as CSV File. Map the document from the trigger, then pick the table Make lists for you.
04
Test with Run once
Click Run once, then edit a document in Grist. Open the small bubble above each module to read the bundles it received. A bundle is one item passed along, here one document.
05
Schedule it and switch it on
Click the clock on the first module. A new scenario checks every 15 minutes by default. Keep it or change it, then flip the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What can start a Grist scenario?

2 modules start a scenario when something happens in Grist. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Grist as soon as it happens.

Grist1Watch Documents

Watch Documents

Scheduled trigger

In Make“Triggers when a document is created or updated.”

This trigger keeps an eye on your Grist documents and starts the scenario when one appears or changes, handing that document to the next modules as one bundle.

How it fires

scheduled. Make checks Grist on the scenario's schedule, so a change shows up at the next check, not the moment it happens.

When to use it

you want a backup, an export or a message to follow each new or edited document.

Watch out

it reacts at document level, so a single edited cell and a brand new document look the same to it. Add a filter after it if you only care about one kind.

Grist2Watch Workspaces

Watch Workspaces

Scheduled trigger

In Make“Triggers when a workspace is created or updated.”

Here the scenario starts whenever a workspace, the folder that groups several Grist documents, is created or updated. Make passes the workspace details down the chain as one bundle.

How it fires

scheduled. Make polls Grist at the rhythm you set on the clock of the first module, 15 minutes by default.

When to use it

a team lead opens a new workspace for a project, and you want the project channel told or the permissions set at the next check.

Watch out

Grist only offers workspaces on team plans, so on a personal space this trigger has nothing to watch.

Modules

Every Grist module in Make, and when to pick it

Grist gives you 29 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Grist1

Add Records to a Table

Action

In Make“Add new records to a specified table.”

Writes fresh rows into the Grist table you choose, filled with data mapped from earlier modules. It is the workhorse for getting outside data into Grist.

When to use it

a lead form, an order or a support ticket arrives in another app and deserves a line in your tracker.

Watch out

it always creates, never checks. Run List Records from a Table first if the same entry might come in twice.

Grist2

Create a Document

Action

In Make“Creates an empty document.”

Opens a blank Grist document from inside a scenario. The document starts empty, so think of it as the container you will fill next with other modules or by hand.

When to use it

every new client or project gets its own document, created the moment the deal closes in your CRM.

Watch out

the new file has no tables yet. Plan the next step, such as a template copied by your team, before counting on rows.

Grist3

Create a Workspace

Action

In Make“Creates an empty workspace. Workspaces are available on team plans.”

Sets up an empty workspace, the Grist folder that holds related documents. Useful when your structure mirrors departments, clients or projects and you want the folder ready before anyone asks.

When to use it

a new department or partner joins and needs a shared space from the first day.

Watch out

workspaces exist only on Grist team plans. On a personal account the module has nowhere to create one.

Grist4

Delete a Document

Action

In Make“Deletes a document.”

Removes a whole Grist document, tables and all. It is the cleanup tool for files that no longer serve a purpose once a project is archived elsewhere.

When to use it

a test document or a closed client file should disappear after its data was exported with an earlier module.

Watch out

there is no undo from Make. Put an export module before it and test with Run once on a throwaway document.

Grist5

Delete a Workspace

Action

In Make“Deletes a workspace.”

Wipes out a workspace in Grist. Pick it when a team or a client relationship ends and the folder has become clutter that confuses people browsing the site.

When to use it

the offboarding flow for a partner, right after their documents were moved or exported.

Watch out

a workspace holds documents. Check what is inside with Get a Workspace before this runs, because Make will not ask for confirmation.

Grist6

Delete Table Rows

Action

In Make“Removes rows from a table.”

Clears specific rows out of a table while the rest of the document stays untouched. Smaller in scope than deleting a document, and much safer for routine tidying.

When to use it

a cancelled order or a withdrawn applicant should vanish from the table that the team reads.

Watch out

you need the right row IDs. Find them first with List Records from a Table so you delete the lines you meant to.

Grist7

Get a Document

Action

In Make“Returns detailed information about a document.”

Fetches the details of one Grist document and hands them to the next module. It reads, it changes nothing.

When to use it

a trigger gives you a document ID and you need the readable name to write a clear Slack message or email subject.

Watch out

this returns information about the document, not the rows inside it. For table contents, reach for the CSV or list modules.

Grist8

Get a Document as Excel File

Action

In Make“Returns the content of the document as an Excel file.”

Turns a whole Grist document into an Excel file that later modules can upload, attach or store. Colleagues who live in spreadsheets get your data in the format they already open.

When to use it

finance or an outside auditor wants the full workbook, not a link to Grist.

Watch out

on the Make Free plan files are capped at 5 MB, so a heavy document may need a paid plan or a single table exported as CSV.

Grist9

Get a Document as SQLite File

Action

In Make“Returns the content of a document, as an SQLite file.”

Pulls out the complete document as an SQLite file, a database file that keeps every table together. That makes it a good snapshot to store.

When to use it

you want backups of important documents saved to cloud storage whenever Watch Documents sees a change.

Watch out

SQLite is not something most colleagues can open. Keep the Excel module for humans and this one for archives.

Grist10

Get a Document Table as CSV File

Action

In Make“Returns the content of a document's table as a CSV file.”

Exports one table, not the whole document, as a CSV file. Lighter than the Excel or SQLite exports and readable by nearly every tool that imports data.

When to use it

a mailing tool, a BI dashboard or a partner only needs the contacts table, not the rest of your workspace.

Watch out

pick the table carefully in the module field. Each run exports only that one, so several tables mean several modules.

Grist11

Get an Organization

Action

In Make“Returns detailed information about a personal space.”

Returns the details of an organization, which is what the Grist API calls a team site or personal space. Handy for adding context to a report or a log line.

When to use it

your scenario touches several team sites and you need the site name in a notification so people know which one changed.

Watch out

you need the organization ID. List Organizations gives it to you if you do not have it yet.

Grist12

Get a Workspace

Action

In Make“Returns detailed information about a workspace.”

Reads the details of one workspace and passes them along. Nothing is changed in Grist, so it is safe to drop anywhere in a scenario for a quick lookup.

When to use it

before you move, rename or delete a workspace, check its current state and its documents.

Watch out

it covers one workspace at a time. For an overview of all of them, List Workspaces is the better starting point.

Grist13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request to any endpoint of the Grist API with the connection you already set up. It fills the gaps when none of the ready-made modules does exactly what you need.

When to use it

you know the Grist API offers something, and none of the 31 modules covers it.

Watch out

you write the request yourself, so keep the Grist API reference open and test with Run once before switching the scenario on.

Grist14

Move a Document

Action

In Make“Moves a document to another workspace in the same organization. Available on a Team Plan.”

Shifts a document from one workspace to another inside the same organization. The content stays intact; only its home changes, along with who finds it there.

When to use it

a project moves from Active to Archive, or a deal moves from sales to delivery, and its document should follow.

Watch out

Grist reserves moving documents to team plans, and both workspaces must belong to the same organization.

Grist15

Update a Document Access

Action

In Make“Changes who has access to a document.”

Changes who can open one specific document. Instead of clicking through sharing settings by hand, the scenario grants or removes access for you.

When to use it

a freelancer signs their contract and should see the project document, then lose access when the mission closes.

Watch out

access mistakes are quiet. Follow it with List a Document Users while testing to confirm the right people ended up on the list.

Grist16

Update a Document Metadata

Action

In Make“Updates an existing document metadata but not its contents.”

Edits the information about a document while leaving its tables and rows alone. A tidy way to keep naming consistent across a busy site.

When to use it

a client renames their company, or a project gets a status prefix like DONE when it wraps up.

Watch out

the content inside is out of reach for this module. To change rows, use Update Records of a Table.

Grist17

Update an Organization

Action

In Make“Updates information about an existing organization.”

Changes the information of an existing organization, the team site that sits above workspaces. Rarely needed, but when it is, the change lives in a flow you tested instead of a manual trip to the settings.

When to use it

an admin flow that keeps site details in line with what your HR or IT tool says.

Watch out

this is the top level of your Grist setup, so try it on a spare organization first.

Grist18

Update a Workspace

Action

In Make“Updates information about the existing workspace.”

Edits the details of a workspace that already exists. The documents inside stay where they are and keep their data.

When to use it

a client project changes name in your CRM and the matching Grist folder should reflect it without anyone remembering to do so.

Watch out

it needs the workspace ID. Get it from Watch Workspaces or List Workspaces earlier in the scenario.

Grist19

Update a Workspace Access

Action

In Make“Changes who has access to the workspace.”

Sets who can reach a whole workspace in one go, rather than document by document. One change opens or closes every file in that folder.

When to use it

a new hire joins a department and needs everything that team keeps in Grist.

Watch out

the reach is wide. A wrong mapping exposes several documents at once, so check the bundle in Run once before activating.

Grist20

Update Organization Access

Action

In Make“Changes who has access to the organization.”

Controls membership of an entire organization, the widest access level Grist has. Adding someone here is how they enter the team site in the first place.

When to use it

your onboarding checklist in another app marks an employee as active, and the Grist site should open to them.

Watch out

removal matters as much as addition. Build the offboarding branch too, and verify it with List Organization Users.

Grist21

Update Records of a Table

Action

In Make“Modifies records of a table.”

Changes values in rows that already exist in a Grist table. Where Add Records creates, this one corrects, so your table stays one line per item.

When to use it

an invoice gets paid in your accounting tool and the matching row in Grist should switch to paid.

Watch out

it needs the row IDs. Look them up first with List Records from a Table, or you will update nothing.

Grist22

List a Document Users

In Make“Returns a list of users with access to a document.”

Returns everyone who has access to one document. As a search module, it can hand back several bundles, one per person, which the next module processes one by one.

When to use it

a client asks who can see their data, or a check right after changing permissions.

Watch out

each person becomes a bundle, so a module placed after it runs once per user and uses operations accordingly.

Grist23

List a Workspace Users

In Make“Returns a list of users that have access to the workspace.”

Gives you the list of people who can reach a workspace. Good for seeing at a glance who sits behind a folder of sensitive documents.

When to use it

before archiving a workspace, notify each member so nobody is surprised.

Watch out

it can return zero people, one or many. Add a filter or an aggregator if you want a single summary message instead of one per user.

Grist24

List Organizations

In Make“Returns a list of personal spaces. Team sites and personal spaces are called 'orgs' in the API.”

Returns the organizations your connection can see. In the Grist API, team sites and personal spaces are both called orgs, so both can show up.

When to use it

the first step of an admin scenario that loops over every site to gather users or workspaces.

Watch out

the results depend on the account behind the API key. A key from a limited account sees fewer sites.

Grist25

List Organization Users

In Make“Returns a list of users with access to org.”

Lists every member of an organization. Where the document and workspace lists are narrow, this one shows who belongs to the whole site.

When to use it

you compare Grist members with your HR tool to catch people who left the company but kept their access.

Watch out

every member is a bundle, so a big team means many runs of the next module. Keep the chain short after it.

Grist26

List Records from a Table

In Make“Returns a list of records.”

Reads rows from a Grist table and sends them down the scenario, one bundle per record. This is how you get data out of Grist to act on it elsewhere.

When to use it

push open tasks to a project tool, or find the row to update before Update Records of a Table.

Watch out

a large table produces many bundles, and each module after it counts one operation per bundle.

Grist27

List Table Columns

In Make“Returns a list of the table's columns.”

Returns the columns of a table, which tells you how the table is built before you read or write in it. A quiet but helpful check.

When to use it

a scenario serves several similar tables and needs to confirm a column exists before writing to it.

Watch out

it describes the structure, not the data. Pair it with List Records from a Table when you need the values too.

Grist28

List Workspaces

In Make“Returns a list of workspaces available in the current domain.”

Gives back the workspaces available in the current domain. It is the overview that most workspace scenarios start from.

When to use it

you want an inventory of team folders sent to a sheet, or the ID of one workspace found by name.

Watch out

it lists workspaces only. To see the documents inside them in the same pass, use List Workspaces within Organization.

Grist29

List Workspaces within Organization

In Make“Returns a list of workspaces and documents within an organization.”

Returns the workspaces of one organization together with the documents they contain. One call gives you the full map of a team site.

When to use it

an audit of what exists where, or a scenario that has to find a document by name without knowing its workspace.

Watch out

you pick the organization first. If you are unsure of its ID, run List Organizations before this module.

Need help

Need help automating Grist with Make?

A person reads every message.

FAQ

Questions people ask after connecting Grist

01Is the Grist Make integration free?

Yes, Grist is a standard app in Make, so it works on the Free plan. That plan limits you to 2 active scenarios, a check every 15 minutes at most, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Your Grist subscription is separate and handled on the Grist side.

02What does it take to connect Grist to Make?

You need an active Grist account and an API key. Create the key in Grist by opening the account menu from your profile picture, going to Profile Settings, scrolling to the API section and clicking Create. Then add any Grist module in Make, click Create a connection, paste the key and save. The same connection then serves all 31 Grist modules in every scenario you build, so you only do this once per account.

03Do Grist triggers fire instantly in Make?

No. Both Grist triggers, Watch Documents and Watch Workspaces, are scheduled. Make checks Grist on the scenario's schedule, every 15 minutes by default, and picks up what changed since the last check. On a paid plan you can shorten the interval to 1 minute. Grist has no instant trigger in Make, so a webhook sent by Grist is not part of the listed modules. Also note that these triggers watch documents and workspaces, not single rows.

04What if a Grist module is missing in Make?

Use Make an API Call. It sends a request to any endpoint of the Grist API through your existing connection, so anything the API allows is reachable even without a dedicated module. Keep in mind that some features depend on your Grist plan: workspaces and moving documents are only available on Grist team plans. If a module fails, check that your plan includes the feature before rebuilding the scenario from scratch or blaming the connection.

05Make or n8n for Grist: which one fits?

It depends on where your other automations already run. Make offers 31 Grist modules, including 2 scheduled triggers and Make an API Call, all set up in a visual editor that you can test with Run once. Grist also has an n8n node, with its own guide. Compare the modules each tool lists for your exact use case, then keep your Grist flows next to the rest of your automations so one team maintains them.

Create an API key in Grist

Add a Grist module in Make

Paste the key and save

Start a new scenario

Add Watch Documents

Add the CSV export

Test with Run once

Schedule it and switch it on

Need help automating Grist with Make?