+
Connect Google Drive to Supabase
Automate Google Drive and Supabase with AI
User uploads and exports in Google Drive sometimes need row level links in Supabase your app reads. Operator.io points OpenClaw at Drive and Supabase so a new file in a watched folder can insert or update the matching storage metadata row, and Supabase queries can return the Drive path when support asks for a user's latest export. Tell it a user ID and it shows Supabase fields with the Drive files tied to them.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Google Drive and Supabase
What your agent does in Google Drive
Insert File Parent (v2)
Tool to add a parent folder for a file using Google Drive API v2. Use when you need to add a file to an additional folder.
Insert Property (v2 API)
Tool to add a property to a file, or update it if it already exists (v2 API). Use when you need to attach custom key-value metadata to a Google Drive file.
Copy file with advanced options
Creates a copy of a file and applies any requested updates with patch semantics. Use when you need to duplicate a file with advanced options like label inclusion, visibility settings, or custom metadata.
Create Comment
Tool to create a comment on a file in Google Drive. Returns a nested `data` object; extract `data.id` for the resulting comment identifier. Omit `anchor` and `quoted_file_content_*` for general file-level comments.
Create Shared Drive
Tool to create a new shared drive. Use when you need to programmatically create a new shared drive for collaboration or storage.
Create File or Folder
Creates a new file or folder in Google Drive. Supports both metadata-only creation (for folders and empty documents) and file upload with content. When file_to_upload is provided, uploads the actual file bytes; otherwise creates an empty...
What your agent does in Supabase
Create project api key
Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.
Delete an API key from the project
Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
Delete third party auth config
Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.
Get a third-party integration
Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.
List third-party auth integrations for project
Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
Update an API key for the project
Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.
How it works
Tell the agent what you want to happen between Google Drive and Supabase, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Google Drive, works out what to do, and runs the matching action in Supabase without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Google Drive and Supabase
- How do I connect Google Drive and Supabase to Operator?
- You authorize Google Drive and Supabase once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Google Drive and Supabase?
- Tell it the job and it moves between Google Drive and Supabase as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Google Drive and Supabase in sync?
- Yes. It can watch Google Drive and act in Supabase, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Google Drive and Supabase integrations
Put your agent on Google Drive and Supabase
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free