• English
    • Google

    Google Drive

    Connect Google Drive to a MeDo app: find files and folders, create text or folders, upload from a URL, download, move, copy, overwrite, and trash an item after confirmation.

    Updated 2026-09-20

    Google Drive is a connector: it links a MeDo app to one Google account, so the app can search that Drive, open file details, create folders and text files, upload from a public URL, download, move or copy, overwrite a file, and trash an item after confirmation. Sharing and permission changes are not included.

    What you can build

    • A private file browser. List a chosen folder, open file details, and refresh on demand.
    • A report backup page. Save a text note or a public URL into a named folder, then confirm it landed.
    • A shared-folder workspace. Keep project files in one folder, copy or move them when the owner names the target, and show the updated layout.
    • A cleanup board. Find files in a folder and trash them only after each item is confirmed.

    Google Drive fits when the app should work with real files the owner already keeps in Drive — browsers, backups, and folder workspaces. It is not a sharing-admin tool and it cannot empty trash, see Limits.

    Build examples

    Copy one of these into the prompt box. The first one is the smallest useful starting point.

    Use @Google Drive to build a private file browser that lists a chosen folder and opens file details.
    Use @Google Drive to build a report backup page that saves a text note or a public URL into a named folder and confirms it landed.
    Use @Google Drive to build a shared-folder workspace that copies or moves a file after I name the target folder.
    Use @Google Drive to build a cleanup board that finds files in a folder and trash them only after I confirm each item.

    The wording matters: say which folder the app should use. "A private browser for the team's reports folder" produces a different app from "a page that lists files".

    Prepare and connect

    You need a Google account that can already open the Drive files the app should use. No API key, no Google Cloud project, and no billing setup are involved.

    1. Open Skills & Connectors in the sidebar and search for Google Drive.
    2. Open the Google Drive card and click Connect.
    3. Sign in to the Google account and approve the access MeDo asks for.
    4. The button changes to Connected. That is the success state; you do not need to copy anything back into the app.

    If you start building before connecting, MeDo notices and shows a Google Drive connection button under its reply. You can connect there instead. If no button appears, use the connector card described above.

    Use it in your app

    • The app uses the owner's connected Drive, not each visitor's Google account. Everyone who reaches a file view sees the same Drive. Keep file browsers, uploads, and trash behind your app's own sign-in, and restrict them to the people who should have that access. A page titled "private" is not access control on its own.
    • Name the folder in the prompt. Paste a folder link or ID when you can; names can collide. The app should show the folder name it actually opened.
    • Reads refresh on demand. There is no live sync with Drive. Add a refresh control rather than expecting new files to appear by themselves.
    • Trash is confirmed first. MeDo asks for confirmation before moving an item to trash. Permanent delete and empty-trash are not available.
    • App-owned data stays in the app. Labels, review status, and notes that are not Drive fields belong in your app's own tables, keyed to the real file ID.

    Limits and troubleshooting

    What you may expectWhat actually happens
    Sharing, permission changes, comments, labels, versionsNot available through this connector.
    Shared Drive administrationNot available. The app works with what the connected account can already open.
    Editing Google Docs, Sheets, or Slides bodiesNot available. Overwrite applies to ordinary files, not Workspace document bodies.
    Permanent delete or empty trashNot available. Confirmed trash moves an item to Drive trash.
    A live feed from DriveNot available. Files are read when the page loads or refreshes.
    Each visitor connecting their own DriveThe connection belongs to the app owner.

    "Connection required" appears in the app. Ask the app owner to open the connector card and click Connect, then reload.

    Search returns the wrong folder. Folder names can collide. Use the folder ID from a previous search result or paste the folder link, then refresh.

    A trash action was refused. Trash needs an explicit confirmation in the app. Check that the confirm step ran before trying again.

    A download link stopped working. Download URLs are short-lived. Request a new download rather than reusing an old link.

    Visitors can see files when they should not. The connection is shared. Add sign-in and server-side restrictions to the app; see Managing access & roles.