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>"
  }
}
Example: the "Create file" tool on an account your customer connected.

How it works

From a connected customer to the first Google Drive call.

  1. 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. 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. 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

See all 12 tools

Connection

How your customer connects the account

Official Google Drive documentation

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 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.