File storage
Google Drive in your product and your AI agents, through one API
The Google Drive toolkit covers files and folders, shared drives, permissions and comments. Your product or AI agent calls them through Connect, which handles the customer's OAuth connection and logs every execution, so you skip building the integration.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/google_drive_create_file/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"name": "<name>"
}
}How it works
From a connected customer to the first Google Drive call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Google Drive account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Google Drive.
Report folders per client
An agency tool copies a report template into the client's folder and shares it with the right people through permissions.
Review on shared documents
A SaaS lists the comments of a Google Doc under review and adds its own comment when a step in the workflow completes.
Agent that finds files
An AI agent searches files by name or type, reads their metadata and webViewLink, and moves or renames them on request.
Tools
12 Google Drive tools
- List filesGETSearches the files and folders the account can see. Each file comes with only id, name and mimeType unless fields asks for more, such as webViewLink, modifiedTime and parents. To leave out the trash, add trashed = false to q. Pass nextPageToken as pageToken to read the next page.
- Get fileGETGets the metadata of a file or folder, not its content. webViewLink is the address that opens it in the browser, and parents has the id of the folder it is in.
- Create filePOSTCreates a file with metadata only, without content: a folder, or an empty Google Doc, Sheet or Slides presentation, chosen by mimeType. Returns id, name and mimeType, plus whatever fields asks for, such as webViewLink.
- Update filePATCHRenames, describes, stars, moves or trashes a file or folder; only the fields sent change. To move it, pass the new folder in addParents and the current one, from the parents of Get file, in removeParents. A folder of My Drive cannot move into a shared drive.
- Copy filePOSTCopies a file, such as a report template, and returns the new file. Without parents the copy stays in the same folder as the original. Folders cannot be copied.
- List shared drivesGETLists the shared drives the account is a member of, with id and name. The id goes in driveId of List files. Pass nextPageToken as pageToken to read the next page.
- List permissionsGETLists who has access to a file or folder. Without fields each permission has only basic fields, such as id, type and role: ask for emailAddress and displayName in fields to see who it is. Pass nextPageToken as pageToken to read the next page.
- Create permissionPOSTShares a file or folder and returns the new permission with its id. Google emails the users and groups it is shared with, unless sendNotificationEmail is false. emailAddress is required for type user or group, and domain for type domain.
- Update permissionPATCHChanges the role or the expiration of an access that already exists, and returns the permission.
- Delete permissionDELETERemoves an access from a file or folder: the user, group, domain or link loses it.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/google_drive, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
Questions about the Google Drive toolkit
Do I need to build against the Google Drive API?
No. Connect ships 12 Google Drive tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Google Drive account?
With the mode the toolkit accepts: OAuth with your product's app. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
