Guide

Google Docs AI Agent: Real Documents, Not Chat Messages

Q: Why did the agent create a document with a title and no body?

Because GOOGLEDOCS_CREATE_DOCUMENT takes its body in a parameter called text, not content. An unrecognized field is dropped silently, so the call succeeds but the document is empty. Use GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN with markdown_text instead.

Q: Does the formatting survive?

Yes with the Markdown actions. Headings, lists, bold, and links render as real Google Docs formatting rather than literal Markdown characters.

Q: Can it edit a document that already exists?

Yes. GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN and GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT edit existing documents, and GOOGLEDOCS_GET_DOCUMENT_PLAINTEXT reads the current contents first.

Q: Do I need Google Drive connected too?

Not for creating or editing documents. Connect Google Drive as well for folder organization, searching for files, or reading non-Docs formats such as PDFs.

An agent that can write to Docs stops producing text you have to copy somewhere. It produces a document with a link. There is one parameter trap between you and that working properly.

What changes when Docs is connected

The output of a good chat session is frequently a document: meeting notes, a proposal, a summary of research, a draft post. Without Docs connected, that output lives in a chat window and your next step is manual. With it connected, the last sentence of the request is “put it in a doc” and you get a link.

That is a small change in mechanics and a large change in whether you actually use the thing.

Connect it in three steps

Open openclawlaunch.com/integrations while signed in.
Find Google Docs and click Connect, then approve the Google account you want documents created in.
Ask for a document in chat. Nothing to configure, nothing to restart.

What the agent actually runs

composio search googledocs create document

composio execute GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN '{"title":"Q3 Report","markdown_text":"# Q3 Report\n\nRevenue held flat."}'

GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN — the one to prefer; takes markdown_text and renders real formatting
GOOGLEDOCS_CREATE_DOCUMENT — plain text, and its body parameter is text
GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN and GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT — edit what is already there
GOOGLEDOCS_GET_DOCUMENT_PLAINTEXT — read the contents back

The blank-document trap

This is worth spelling out because it produces a failure that does not look like a failure. Composio actions drop parameters they do not recognize, silently. So if an agent guesses that the body field is called content — which is the natural English word, and wrong for these actions — the call returns success, the document appears in your Drive, and it contains a title and nothing else.

Two habits avoid it entirely. First, prefer the Markdown action, whose parameter is markdown_text and which also accepts content as an alias. Second, verify: after creating a document, a careful agent reads it back with GOOGLEDOCS_GET_DOCUMENT_PLAINTEXT before telling you it is ready. The create response only returns metadata, so “success” in the response is not evidence that the body landed.

Things worth asking for

“Write up what we just discussed as a doc called Migration Plan.”
“Read the proposal doc and tell me what a skeptical client would push back on.”
“Add a risks section to the end of the launch doc.”
“Turn this email thread into meeting notes with action items at the top.”
“Draft the doc, then email the link to the team.”

The last one needs Gmail connected alongside. Most of the value in these integrations shows up in combinations, not individually.

Limits and revoking access

100 executed actions a day on free trial and Lite, 1,000 on Pro; discovery calls are free. Adding your own Composio API key on the integrations page removes the cap. Disconnect there too — it takes effect on the next call the agent makes.

Frequently asked questions

Why did the agent create a document with a title and no body?

This is the classic Docs failure and it has a specific cause. GOOGLEDOCS_CREATE_DOCUMENT takes its body in a parameter called text, not content. Pass content and the field is silently dropped — the call succeeds, the document is created, and it is empty. Use GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN with markdown_text instead and you get formatting as a bonus.

Does the formatting survive?

With the Markdown actions, yes — headings, lists, bold, and links render as real Google Docs formatting rather than literal asterisks. This is the main reason to prefer the Markdown variants over the plain-text ones for anything a person will read.

Can it edit a document that already exists?

Yes. GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN and GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT handle edits, and GOOGLEDOCS_GET_DOCUMENT_PLAINTEXT lets the agent read the current contents first — which it should, before rewriting anything you care about.

Do I need Google Drive connected too?

Not for creating and editing documents. Connect Drive as well when you want the agent to organize files into folders, find a document by searching rather than by ID, or read non-Docs files like PDFs.