Grist and Google Drive Integration

In the workspace, click the “Create New Scenario” button.

Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Grist, triggered by another scenario, or executed manually (for testing purposes). In most cases, Grist or Google Drive will be your first step. To do this, click "Choose an app," find Grist or Google Drive, and select the appropriate trigger to start the scenario.

Select the Grist node from the app selection panel on the right.

+

1

Grist

Click on the Grist node to configure it. You can modify the Grist URL and choose between DEV and PROD versions. You can also copy it for use in further automations.

+

1

Grist

Node type

#1 Grist

/

Name

Untitled

Connection *

Select

Map

Connect Grist

Sign In

⏵

Run node once

CancelSave

Next, click the plus (+) icon on the Grist node, select Google Drive from the list of available apps, and choose the action you need from the list of nodes within Google Drive.

1

Grist

⚙

+

2

Google Drive

Now, click the Google Drive node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Google Drive settings. Authentication allows you to use Google Drive through Latenode.

1

Grist

⚙

+

2

Google Drive

Node type

#2 Google Drive

/

Name

Untitled

Connection *

Select

Map

Connect Google Drive

Sign In

⏵

Run node once

CancelSave

Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.

1

Grist

⚙

+

2

Google Drive

Node type

#2 Google Drive

/

Name

Untitled

Connection *

Select

Map

Connect Google Drive

Google Drive Oauth 2.0

#66e212yt846363de89f97d54

Change

Select an action *

Select

Map

The action ID

⏵

Run node once

CancelSave

Use various Latenode nodes to transform data and enhance your integration:

• Branching: Create multiple branches within the scenario to handle complex logic.
• Merging: Combine different node branches into one, passing data through it.
• Plug n Play Nodes: Use nodes that don’t require account credentials.
• Ask AI: Use the GPT-powered option to add AI capabilities to any node.
• Wait: Set waiting times, either for intervals or until specific dates.
• Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
• Iteration: Process arrays of data when needed.
• Code: Write custom code or ask our AI assistant to do it for you.

5

JavaScript

⚙

6

AI Anthropic Claude 3

⚙

+

7

Google Drive

1

Trigger on Webhook

⚙

2

Grist

⚙

⚙

3

Iterator

⚙

+

4

Webhook response

After configuring Grist, Google Drive, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.

Run the scenario by clicking “Run once” and triggering an event to check if the Grist and Google Drive integration works as expected. Depending on your setup, data should flow between Grist and Google Drive (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.