Saltar al contenido principal

Documentation Index

Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt

Use this file to discover all available pages before exploring further.

Google Drive is Google Workspace’s shared file system. Unlike structured-data integrations such as Sheets or Supabase, Drive operates on files and folders: documents, PDFs, images, contracts, and any asset you need to store, organize, or share as part of a process. In Brain Studio, this integration lets your flows create, search, share, and organize files in Drive directly from the conversation, without anyone opening Drive separately.

​
What Google Drive enables

When you connect Google Drive, you can:
  • Deliver documents to customers from chat — find a file, adjust permissions, and share a link without anyone manually navigating folders
  • Receive and classify user files — upload attachments to the right folder with consistent naming by customer, case, or process
  • Provision structure by customer or project — create folders, copy templates, and share with the assigned team automatically
  • Govern collaboration and permissions — share resources, resolve access proposals, and work with document comments
  • Check metadata and context — identify paths, versions, and current user details before making flow decisions

​
Installation

​
Prerequisites

  1. A Google account with access to Google Drive.
  2. Sufficient permissions on the resources you will manage (comments, sharing, or shared drives, as applicable).

​
How to connect it

You can connect Google Drive in two ways:
  • From Marketplace — find the integration and connect it manually.
  • From Jelou Agent — if the agent detects you need Drive while building a solution, it will ask you to connect it at that moment.
If you are creating a solution from scratch, the most common approach is connecting Google Drive from Jelou Agent. If you already know which integration you need, you can install it manually from Marketplace.
In both cases, access is done through OAuth in a secure Google window.

How to use integrations in Brain

Installation with Jelou Agent or Marketplace, and usage in Canvas versus AI Agent.

Jelou Agent

How to describe your solution so Brain suggests integrations and builds the flow.
The following flow describes manual installation from Marketplace.
1

Open Marketplace

In Brain Studio, open Marketplace from the side menu.
2

Search Google Drive

Find Google Drive in the catalog and click Connect.
3

Authorize access with Google

A secure Google authorization window will open. Sign in if needed and accept the requested permissions.
4

Confirm installation

Back in Brain Studio, complete the wizard until the integration appears as connected.
In Marketplace, Google Drive should appear as connected. From Canvas you can add its node, and in AI Agent → Tools you can enable it.

​
Available tools

At a high level, actions are grouped as:
  • Query — search/list files, folders, drives, comments, replies, and metadata.
  • Create or modify — create, copy, upload, move, update, and share resources.
  • Collaboration and governance — comments, replies, access proposals, and permissions.
  • Delete — move to trash or permanently delete resources.
This integration exposes 37 tools in Brain Studio; below is each tool with purpose, inputs, and example.

​
Features

Adds an unanchored comment to a supported file (e.g. Google Doc): general feedback without highlighting specific text.Inputs:
  • fileId (string) — File ID.
  • content (string) — Comment text (HTML allowed per API).
Example:
{
  "fileId": "1XyZdocId",
  "content": "Please review the conclusions section before publishing."
}
Google documentation: comments.create
Creates a sharing permission on a file or folder and may return a sharing URL depending on configuration.Inputs:
  • fileId (string) — File or folder ID.
  • role (enum: reader | writer | commenter | owner) — Access level.
  • type (enum: user | group | domain | anyone) — Grantee type.
  • emailAddress (optional, string) — Email when type is user or group.
  • domain (optional, string) — Domain when type is domain.
  • sendNotificationEmail (optional, boolean) — Send email notification.
Example:
{
  "fileId": "1XyZarchivoID",
  "role": "writer",
  "type": "user",
  "emailAddress": "[email protected]",
  "sendNotificationEmail": true
}
Google Help: how sharing works · permissions.create
Creates a copy of a file in your Drive (or another supported location).Inputs:
  • fileId (string) — Source file ID.
  • name (optional, string) — Name for the copy.
  • folderId (optional, string) — Destination folder.
Example:
{
  "fileId": "1XyZarchivoID",
  "name": "report-copy.pdf",
  "folderId": "1A2B3CcarpetaID"
}
Google documentation: files.copy
Creates a Google Doc from a template. You can define placeholders in the template that the action replaces with values.Inputs:
  • templateFileId (string) — Template document ID.
  • name (optional, string) — Title of the new document.
  • folderId (optional, string) — Destination folder.
  • placeholders / replacements (optional, object) — Key-value map (exact field names per Brain Studio).
Placeholder replacement often follows mustache-style conventions; check the integration package for the exact placeholder format.
Example:
{
  "templateFileId": "1TplAbC123",
  "name": "Contract - Client X",
  "folderId": "1A2B3CcarpetaID",
  "placeholders": {
    "{{name}}": "Jane",
    "{{date}}": "2025-03-23"
  }
}
Google: files / Docs · google-docs-mustaches (placeholders)
Creates a new file with plain text content (e.g. .txt or indicated MIME type).Inputs:
  • name (string) — File name.
  • content (string) — Plain text body.
  • mimeType (optional, string) — Often defaults to text/plain.
  • folderId (optional, string) — Parent folder.
Example:
{
  "name": "notes.txt",
  "content": "Line 1\\nLine 2",
  "mimeType": "text/plain",
  "folderId": "1A2B3CcarpetaID"
}
Google documentation: files.create
Creates an empty folder at the given location.Inputs:
  • name (string) — Folder name.
  • parentFolderId (optional, string) — Parent folder.
  • description (optional, string) — Description.
Example:
{
  "name": "Documents 2025",
  "parentFolderId": "0B1XyZpadreID",
  "description": "Documents for 2025"
}
Google documentation: files.create (folder type)
Creates a new shared drive (Team Drive).Inputs:
  • name (string) — Shared drive name.
  • requestId (optional, string) — Idempotent request ID if required by the API.
Example:
{
  "name": "Project Alpha"
}
Google documentation: drives.create
Deletes a comment by ID (you must own the comment or have file permissions).Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd"
}
Google documentation: comments.delete
Permanently deletes a file or folder; it does not move it to trash.Inputs:
  • fileId (string) — Resource ID.
This maps to API files.delete and is destructive. To trash an item, use Move file to trash instead.
Example:
{
  "fileId": "1XyZarchivoID"
}
Google documentation: files.delete
Deletes a specific reply to a comment.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
  • replyId (string) — Reply ID.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd",
  "replyId": "reply-id-123"
}
Google documentation: replies.delete
Deletes a shared drive only when it is empty (no content).Inputs:
  • driveId (string) — Shared drive ID.
The API typically requires the drive to contain no files or folders. Empty the drive first or use other tools to move or delete content.
Example:
{
  "driveId": "0AJxyZunidadID"
}
Google documentation: drives.delete
Downloads file content. The connector may return base64 for small files or a download URL for large files.Inputs:
  • fileId (string) — File ID.
Example:
{
  "fileId": "1XyZarchivoID"
}
Google documentation: downloads
Searches for files using supported criteria (e.g. name or q query).Inputs:
  • name (optional, string) — Name or fragment.
  • query (optional, string) — Files search query.
  • pageSize (optional, number) — Result limit.
Example:
{
  "name": "report",
  "pageSize": 20
}
Google documentation: search files and folders
Searches for folders by name or other supported query.Inputs:
  • name (optional, string) — Folder name.
  • query (optional, string) — Query (e.g. mimeType = 'application/vnd.google-apps.folder').
Example:
{
  "name": "Billing",
  "query": "mimeType = 'application/vnd.google-apps.folder' and name contains 'Billing'"
}
Google documentation: search files and folders
Lists or searches Google Forms by name (Forms MIME type).Inputs:
  • name (optional, string) — Form name.
  • query (optional, string) — Custom query.
Example:
{
  "name": "Satisfaction survey",
  "query": "mimeType = 'application/vnd.google-apps.form'"
}
Google documentation: search files and folders
Searches for Google Sheets by name.Inputs:
  • name (optional, string) — Spreadsheet name.
  • query (optional, string) — Query (e.g. mimeType = 'application/vnd.google-apps.spreadsheet').
Example:
{
  "name": "Sales Q1",
  "query": "mimeType = 'application/vnd.google-apps.spreadsheet' and name contains 'Sales'"
}
Google documentation: search files and folders
Gets a specific comment by commentId on a file.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd"
}
Google documentation: comments.get
Returns authenticated account information via about.get: name, email, storage used, quota, etc.Inputs:
  • fields (optional, string) — Fields to return per API.
Example:
{
  "fields": "user,storageQuota"
}
Google documentation: about.get
Gets file or folder metadata by fileId.Inputs:
  • fileId (string) — File ID.
  • fields (optional, string) — Fields to include.
Example:
{
  "fileId": "1XyZarchivoID",
  "fields": "id,name,mimeType,parents,webViewLink"
}
Google documentation: files.get
Resolves the folderId for the last segment of a path (e.g. Folder1/Folder2), optionally creating missing folders.Inputs:
  • path (string) — Path with separators (format shown in Brain Studio).
  • rootFolderId (optional, string) — Root folder if not default “My Drive”.
  • createMissing (optional, boolean) — Create missing folders.
Example:
{
  "path": "Clients/2025/Contracts",
  "createMissing": true
}
Google documentation: search files and folders
Gets a specific reply on a comment.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
  • replyId (string) — Reply ID.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd",
  "replyId": "reply-id-123"
}
Google documentation: replies.get
Gets metadata for one shared drive by ID or, depending on parameters, accessible drives.Inputs:
  • driveId (optional, string) — Shared drive ID; if omitted, behavior depends on the tool (e.g. list all).
Example:
{
  "driveId": "0AJxyZunidadID"
}
Google documentation: drives.get
Lists access proposals for a file or folder (Drive access request flows).Inputs:
  • fileId (string) — File or folder ID.
Example:
{
  "fileId": "1XyZarchivoID"
}
Google documentation: accessProposals.list
Lists all comments on a file.Inputs:
  • fileId (string) — File ID.
  • pageSize (optional, number) — Page size.
  • pageToken (optional, string) — Pagination.
Example:
{
  "fileId": "1XyZdocId",
  "pageSize": 50
}
Google documentation: comments.list
Lists files in a folder or using other supported criteria (files.list).Inputs:
  • folderId (optional, string) — Parent folder.
  • pageSize (optional, number) — Page size (often max 100).
  • pageToken (optional, string) — Next page token.
  • query (optional, string) — Additional filter.
  • orderBy (optional, string) — Sort order (e.g. modifiedTime desc).
Example:
{
  "pageSize": 25,
  "pageToken": "CAoQAA",
  "folderId": "1A2B3CcarpetaID",
  "query": "mimeType != 'application/vnd.google-apps.folder'",
  "orderBy": "modifiedTime desc"
}
Google documentation: files.list
Lists replies for a specific comment.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd"
}
Google documentation: replies.list
Moves a file or folder by updating parents to the destination folder.Inputs:
  • fileId (string) — Item to move.
  • targetFolderId (string) — Destination folder ID.
Example:
{
  "fileId": "1XyZarchivoID",
  "targetFolderId": "1A2B3CnuevaCarpetaID"
}
Google documentation: files.update (parents)
Marks the file or folder as trashed without permanent deletion.Inputs:
  • fileId (string) — Resource ID.
Example:
{
  "fileId": "1XyZarchivoID"
}
Google documentation: files.update
Adds a reply to an existing comment.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
  • content (string) — Reply text.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd",
  "content": "Done — section 3 reviewed."
}
Google documentation: replies.create
Accepts or denies an access proposal for a file or folder.Inputs:
  • fileId (string) — Resource ID.
  • proposalId (string) — Proposal ID.
  • action (enum) — API-supported value (e.g. accept / deny).
Example:
{
  "fileId": "1XyZarchivoID",
  "proposalId": "prop-abc-123",
  "action": "accept"
}
Google documentation: accessProposals.resolve
Marks a comment as resolved (closes the review thread in Docs UI).Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
  • resolved (optional, boolean) — Usually true to resolve.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd",
  "resolved": true
}
Google documentation: comments.update
Searches shared drives with a query (q) and pagination options.Inputs:
  • query (optional, string) — Search criteria.
  • pageSize (optional, number)
  • pageToken (optional, string)
Example:
{
  "query": "name contains 'Marketing'",
  "pageSize": 10
}
Google documentation: search shared drives
Updates content of an existing comment.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
  • content (string) — New text.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd",
  "content": "Updated comment text."
}
Google documentation: comments.update
Updates metadata (name, description, parents) and/or content depending on file type.Inputs:
  • fileId (string) — File ID.
  • name (optional, string) — New name.
  • description (optional, string) — Description.
  • content (optional, string) — Base64 content for manageable binary files.
  • mimeType (optional, string) — Required when updating content.
Example:
{
  "fileId": "1XyZarchivoID",
  "name": "report-updated.pdf",
  "description": "Corrected version",
  "content": "JVBERi0xLjQKJcTl8uXrp/Og0MTGCg==",
  "mimeType": "application/pdf"
}
Google documentation: files.update
Edits the text of a reply to a comment.Inputs:
  • fileId (string) — File ID.
  • commentId (string) — Comment ID.
  • replyId (string) — Reply ID.
  • content (string) — New content.
Example:
{
  "fileId": "1XyZdocId",
  "commentId": "AAA-BbCcDd",
  "replyId": "reply-id-123",
  "content": "Update: now published."
}
Google documentation: replies.update
Updates shared drive metadata (e.g. name, restrictions per API).Inputs:
  • driveId (string) — Shared drive ID.
  • name (optional, string) — New name.
  • Other fields per Brain Studio form.
Example:
{
  "driveId": "0AJxyZunidadID",
  "name": "Project Alpha (archived)"
}
Google documentation: drives.update
Uploads a new file to Drive from a URL or base64 content, with optional folder and description.Inputs:
  • name (string) — File name.
  • mimeType (string) — MIME type.
  • source (enum: url | base64) — Content source.
  • content (string) — URL or encoded data.
  • folderId (optional, string) — Destination folder.
  • description (optional, string) — Description.
Example:
{
  "name": "report.pdf",
  "mimeType": "application/pdf",
  "source": "url",
  "content": "https://example.com/files/report.pdf",
  "folderId": "1A2B3CcarpetaID",
  "description": "Monthly sales report"
}
Google documentation: uploads

​
How to use in Brain

Once connected, you can use Google Drive in two surfaces:

​
In AI Agent

Ideal when users want to search, upload, share, or comment on files in natural language.
1

Open the AI Agent node

In Canvas, select or add the AI Agent node.
2

Open Tools

In the right panel, open the Tools tab.
3

Add Google Drive

Use Add tool, search for Google Drive, and enable it.
4

Configure tools

Choose the full integration or enable only the actions you need. Adjust the prompt to confirm file, folder, or fileId before sharing or deleting, and to ask for clarification when intent is ambiguous.
Google Drive appears in the agent tools list and you can open its settings using the gear icon.
The agent will automatically decide when to search, upload, or share files based on the conversation.

​
In Canvas

Ideal when you need full flow control (for example: upload file → adjust permissions → notify).
1

Drag Google Drive into Canvas

In the side panel, open Marketplace and drag Google Drive into the flow.
2

Select the tool

With the node selected, in Tools choose the action (for example Upload file).
3

Configure request body and memory

Fill in the request body JSON and, if needed, Save response to a memory variable.
4

Connect the flow

Link the Task completed and An error occurred outputs to the next nodes.
The node is ready to run in the order defined by your flow.
Configuration example: The node editor shows a JSON body aligned with the upload or management tool you choose (this example is for uploading a file from URL). Adjust mimeType, source, and content according to the tool form. 
{
  "name": "{{$memory.file_name}}",
  "mimeType": "application/pdf",
  "source": "url",
  "content": "{{$memory.file_url}}",
  "folderId": "{{$memory.folder_id}}"
}
If you build with Jelou Agent, the system automatically decides how to use the integration: it can configure it inside an AI Agent or as a Canvas node, depending on the process type.

​
Use cases

The customer asks for an invoice, contract, or certificate via chat. Instead of searching manually in shared folders, the flow locates it in Drive, adjusts permissions, and delivers the link in the same conversation.Specific example: a financial services company receives certificate requests on WhatsApp. The customer asks for “my 2024 withholding certificate.” The flow finds the file in the customer folder, grants read access, and replies with the direct link. The customer downloads it in seconds without human intervention.Ideal for: utilities, fintech, education, and services with recurring documents customers request frequently.
Files sent by users in chat are saved to the correct Drive folder with consistent naming, instead of ending up scattered in personal inboxes.Specific example: a KYC onboarding process. The customer sends a photo of their identity document via WhatsApp. The flow identifies the customer, resolves the case folder in Drive, uploads the file with a standardized name (e.g. “ID-name-date.jpg”), and confirms receipt. The compliance team finds everything organized when reviewing the case.Ideal for: KYC onboarding, evidence-based support, document operations, and compliance.
Every new customer or opportunity gets folder structure, copied templates, and assigned permissions before work starts.Specific example: a B2B consultancy closes a new project. The flow creates the project folder in Drive, copies standard templates (proposal, contract, meeting notes), shares the folder with the assigned team, and logs the link in the CRM. On day one, everything is ready without manual folder setup.Ideal for: B2B sales, implementation, and account-based projects that need homogeneous structure.

​
Integrations that combine well with Google Drive

After generating or locating a file in Drive, the flow can send it as a link in an email from the connected Gmail account, with permissions already set.Combined flow: file generated in Drive → email via Gmail with shared link to recipient.Gmail documentation
Each uploaded or generated file can be logged as a row in a control sheet: customer, document type, date, link, and status. Useful for audits or operations tracking.Combined flow: file uploaded to Drive → new row in Sheets with metadata and link.Google Sheets documentation
When the commercial process generates documents (proposals, contracts), the flow can create the file in Drive and log the link in the corresponding HubSpot deal or contact.Combined flow: proposal generated in Drive → link logged in HubSpot deal.HubSpot documentation
When scheduling a meeting, the flow can create the materials folder in Drive and attach the link to the event, so attendees have access before the call.Combined flow: event created in Google Calendar → materials folder created in Drive → link attached to event.Google Calendar documentation

Integrations

Catalog of integrations available in Marketplace.

How to use integrations in Brain

General flow for installing and using integrations in Brain Studio.