Skip to content
API Reference

Google Drive

Version: unreleased · Docs: 3c6ab9f2Download Markdown

Use Google Drive to find files, read their content, and create a file or folder in a chosen destination. Use the Drive connector when you want ongoing imports into Knowledge.

Open Customize → Plugins and select this plugin. Add installs an available package; Uninstall means it is already installed. An offered Update refreshes its package version. Your deployment and administrator policy determine availability.

When Add Account is offered, follow its connection instructions using an authorized account that owns or can access the intended resource. If several accounts are connected, check the selected account and Default before the task. Reconnect refreshes an expired connection; an administrator setup notice needs administrator configuration.

Enable the plugin for the selected agent or task. On an installed plugin’s Tools table, check Enabled and the Approval setting for the operations you intend to use. New tasks use these settings; a pending approval still needs a decision. See agent setup and action approvals.

Use Google Drive plugin in Redbelt

Plugin details under Customize → Plugins. The button shows the current installation state.

The Drive Tools table shows Enabled and Approval settings for each operation.

  1. Search for your destination folder, inspect the results, and select its folder ID. Confirm the account and destination if several matches exist.
  2. List that folder’s items to check whether a checklist already exists.
  3. Ask Redbelt to draft Project Checklist using the actions, owners, dates, and approvals in your notes.
  4. Review the file name, content, and destination. Request file creation only when those are correct.
  5. Open the returned Drive result and check the saved content. Use the returned file ID for later reads.

With the Drive plugin enabled, prepare a file called Project Checklist from the notes I attach. Include each action, owner, and deadline supplied in those notes. Ask me which Drive folder to use, then show me the content and destination before creating it.

Creating a file can use text content, an existing artifact, or a supported source URL. Specify the intended MIME type when it matters. Folder creation uses the folder option; a folder ID and its browser URL are different inputs.

Search finds candidates; listing reveals the contents of a selected folder; reading fetches a particular file’s content. Native Docs, Sheets, and Slides have their own plugins for structured edits. The Drive catalog’s metadata update entry is currently disabled, so do not rely on it for renaming, moving, or editing an existing file.

For continuous synchronization, see the Drive connector. Adding this plugin alone does not import files into Knowledge.

Thread and workflow availability are listed separately. A tool must also be enabled for your task and allowed by its account and administrator policy. Configure workflow app actions using only actions offered by the current picker.

Tool Required Fields Thread Workflow
google_drive.create_file file_name Yes Yes
google_drive.get_file_content file_id Yes No
google_drive.list_items No mandatory top-level fields Yes Yes
google_drive.search_files query Yes Yes

Required fields above are the schema minimum. The target, selected operation, or account can impose additional requirements.

google_drive.create_file — Create a file in Google Drive. Optional fields: artifact_id, content, folder_id, is_folder, mime_type, source_url.

google_drive.get_file_content — Read content from a Google Drive file.

google_drive.list_items — List Google Drive items in a folder. Optional fields: folder_id, page_size.

google_drive.search_files — Search Google Drive files. Optional fields: page_size.

For an empty search or not-found error, confirm the connected account can see the exact folder. If a write timed out, search and inspect the destination before retrying.

Provider details: Google Drive help.