Each literature review round produces a new summary document — "Lit Review Round 4 — April 2026". In your current workflow, how do you create it?
read_doc from Day 20 reads the existing draft. For a new doc, I'd go to Google Drive, click "New", name it with the round number. One minute of clicking every month.
GOOGLEDOCS_CREATE_DOCUMENT creates the doc with a title and returns the new document's ID. You can then share it with co-authors, add it to the citations folder, or immediately append content via the Drive API. The response gives you everything you need to reference it:
result = toolset.execute_action(
Action.GOOGLEDOCS_CREATE_DOCUMENT,
{"title": title}
)
new_doc_id = result.get("documentId", "")
The response key is documentId — different from doc_id I passed to read_doc. Why?
The document_id you pass as input is what you chose as the parameter name. The documentId in the response is the key the Docs API uses in its response shape — it's a different field, not the same variable. The value is the new document's ID, which you'd save and use in subsequent calls. Check the response with result.keys() on your first run to confirm the field name.
So create_doc returns the new document ID, and I immediately pass it to append_row or some future write action to populate the summary content? The entire monthly lit-review workflow becomes one script.
Monthly. Automated. Reproducible. Every summary doc named consistently, created in seconds, referenced by ID in your audit trail:
def create_doc(title: str) -> dict:
result = toolset.execute_action(
Action.GOOGLEDOCS_CREATE_DOCUMENT,
{"title": title}
)
print(f"Created doc: {result.get('documentId', 'unknown')}")
return result
Week 3 complete. I can read and write to Sheets, read and create Docs. The capstone Week 4 pipeline just needs chaining.
One operational note: GOOGLEDOCS_CREATE_DOCUMENT creates the document in your Drive root by default — not in a specific folder. If you want the doc in a project folder, use the Drive API's file-move operation after creation, or create it with the Drive files.create endpoint directly. For now, creating in root and moving manually is fine for monthly cadence.
result = toolset.execute_action(
Action.GOOGLEDOCS_CREATE_DOCUMENT,
{"title": "Lit Review Round 4 — April 2026"}
)
new_doc_id = result.get("documentId", "")| Field | Meaning |
|---|---|
documentId | The new document's ID — use for subsequent reads/writes |
title | Confirmed title |
revisionId | Initial revision identifier |
Consistent naming makes search_sheets-style discovery easier later. Use a format like "Lit Review — {round} — {date}" so search by title is deterministic.
Each literature review round produces a new summary document — "Lit Review Round 4 — April 2026". In your current workflow, how do you create it?
read_doc from Day 20 reads the existing draft. For a new doc, I'd go to Google Drive, click "New", name it with the round number. One minute of clicking every month.
GOOGLEDOCS_CREATE_DOCUMENT creates the doc with a title and returns the new document's ID. You can then share it with co-authors, add it to the citations folder, or immediately append content via the Drive API. The response gives you everything you need to reference it:
result = toolset.execute_action(
Action.GOOGLEDOCS_CREATE_DOCUMENT,
{"title": title}
)
new_doc_id = result.get("documentId", "")The response key is documentId — different from doc_id I passed to read_doc. Why?
The document_id you pass as input is what you chose as the parameter name. The documentId in the response is the key the Docs API uses in its response shape — it's a different field, not the same variable. The value is the new document's ID, which you'd save and use in subsequent calls. Check the response with result.keys() on your first run to confirm the field name.
So create_doc returns the new document ID, and I immediately pass it to append_row or some future write action to populate the summary content? The entire monthly lit-review workflow becomes one script.
Monthly. Automated. Reproducible. Every summary doc named consistently, created in seconds, referenced by ID in your audit trail:
def create_doc(title: str) -> dict:
result = toolset.execute_action(
Action.GOOGLEDOCS_CREATE_DOCUMENT,
{"title": title}
)
print(f"Created doc: {result.get('documentId', 'unknown')}")
return resultWeek 3 complete. I can read and write to Sheets, read and create Docs. The capstone Week 4 pipeline just needs chaining.
One operational note: GOOGLEDOCS_CREATE_DOCUMENT creates the document in your Drive root by default — not in a specific folder. If you want the doc in a project folder, use the Drive API's file-move operation after creation, or create it with the Drive files.create endpoint directly. For now, creating in root and moving manually is fine for monthly cadence.
result = toolset.execute_action(
Action.GOOGLEDOCS_CREATE_DOCUMENT,
{"title": "Lit Review Round 4 — April 2026"}
)
new_doc_id = result.get("documentId", "")| Field | Meaning |
|---|---|
documentId | The new document's ID — use for subsequent reads/writes |
title | Confirmed title |
revisionId | Initial revision identifier |
Consistent naming makes search_sheets-style discovery easier later. Use a format like "Lit Review — {round} — {date}" so search by title is deterministic.
Create a free account to get started. Paid plans unlock all tracks.