Google Docs

Google Docs is a connector: it links a MeDo app to one Google account, so the app can search that account's Docs, open a title and link, read visible plaintext, create or copy a document, append markdown, fill literal placeholders, and replace a whole document after confirmation. Folder picking, Drive file lists, PDF export, comments, and delete are not included.

#What you can build

• A private document finder. Search Docs, pick one, and show its title, link, and plaintext.
• A proposal writer. Create a new Google Doc from markdown you review, then show the title and link.
• A template filler. Copy a selected Doc and replace literal placeholders after you preview the find and replace text.
• A meeting-notes workspace. Append markdown to a chosen Doc, and replace the whole document only after you confirm.

Google Docs fits when the app should work with real documents the owner already keeps in Docs — finders, proposal pages, template fills, and notes. It is not a Drive browser and it cannot delete documents, see Limits.

#Build examples

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

Use @Google Docs to build a private document finder where I search my Docs, pick one, and see its title, link, and plaintext.

Use @Google Docs to build a private proposal writer that creates a new Google Doc from markdown I review, then shows the title and link.

Use @Google Docs to build a template filler that copies a selected Doc and replaces literal placeholders after I preview the find and replace text.

Use @Google Docs to build a meeting-notes workspace that appends markdown to a chosen Doc, and can replace the whole document only after I confirm.

The wording matters: name the document or search you mean. "Fill the Q3 contract template" produces a different app from "a page that lists documents".

#Prepare and connect

You need a Google account that can already open the Docs 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 Docs.
2. Open the Google Docs 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 Docs 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 Docs, not each visitor's Google account. Everyone who reaches a document view sees the same Docs. Keep finders and writes 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.
• Start from a document ID or a narrow search. Show the returned title and link before writing. New documents and copies land in the owner's My Drive root; this connector cannot choose a folder.
• Metadata is not the body. Title and link come from a document lookup. Visible text comes from plaintext. Do not expect the metadata call to return the full document.
• Placeholder fill is literal text. Replacements match exact strings, not regular expressions.
• Whole-document replace is confirmed first. MeDo asks for confirmation before overwriting an entire Doc.
• Reads refresh on demand. There is no live sync with Google Docs. Add a refresh control rather than expecting new text to appear by itself.
• App-owned data stays in the app. Labels, review status, and notes that are not Doc fields belong in your app's own tables, keyed to the real document ID.

#Limits and troubleshooting

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

Search returns the wrong document. Titles can collide. Use the document ID from a previous result or paste the Doc link, then refresh.

A whole-document replace was refused. Replacing the entire Doc needs an explicit confirmation in the app. Check that the confirm step ran before trying again.

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

#Related

• Connector catalog — the other connectors and what they are for.
• Google Drive — files and folders, not document bodies.
• Google Sheets — spreadsheet ranges, not Docs.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing access & roles — restrict who can read and change connected data.