+
Connect GitHub to Google Drive
Automate GitHub and Google Drive with AI
Build artifacts and compliance PDFs land in Google Drive while the source code lives in GitHub. Your Operator agent on OpenClaw attaches release bundles from GitHub Actions output to the Drive folder your team uses, updates the README link on the repo when a doc moves, and finds the contract file when legal asks from chat. Ask for everything tied to v2.4 and it lists Drive files beside the GitHub tag and release notes.
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 GitHub and Google Drive
What your agent does in GitHub
Abort Repository Migration
Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions
Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...
Add a repository collaborator
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...
Add assignees to an issue
Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...
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...
How it works
Tell the agent what you want to happen between GitHub and Google Drive, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from GitHub, works out what to do, and runs the matching action in Google Drive 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 GitHub and Google Drive
- How do I connect GitHub and Google Drive to Operator?
- You authorize GitHub and Google Drive 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 GitHub and Google Drive?
- You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right GitHub and Google Drive actions on its own, so you do not map fields or pick triggers.
- Can my agent keep GitHub and Google Drive in sync?
- Yes. It can watch GitHub and act in Google Drive, 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.
GitHub and Google Drive integrations
Put your agent on GitHub and Google Drive
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