Start free
ActionGoogle DocsUpdated June 2026

How do I fetch a Google Doc's content?

Short answer: You can get google doc in Google Docs by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Docs Get Google Doc action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Google Doc in Google Docs — start free All 5 Google Docs actions
Get Google Doc in Google Docs — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Document ID
documentId
stringRequiredDocument ID
Sample request
{
  "documentId": "{{trigger.documentId}}"
}
Returns
{
  "body": {
    "content": [
      {
        "paragraph": {
          "elements": [
            {
              "textRun": {
                "content": "Hello world"
              }
            }
          ]
        }
      }
    ]
  },
  "title": "My Document",
  "documentId": "doc123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Google Doc.

Any of these apps can fire this action as part of a workflow.

Gmail → Google Docs
1 Gmail triggers
Slack → Google Docs
13 Slack triggers
Google Sheets → Google Docs
2 Google Sheets triggers
HubSpot → Google Docs
18 HubSpot triggers
FAQ

Questions about Get Google Doc.

What does the Get Google Doc action do in Google Docs?
Returns the doc as a structural tree (paragraphs, tables, runs). For "extract plain text" workflows, walk the tree and concatenate textRun content. For structured workflows, preserve the tree for round-tripping back into the doc.
What inputs does Get Google Doc require?
Required: Document ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Google Docs returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get Google Doc support batch operations?
Yes. Run Get Google Doc inside a Loop node to process arrays. TinyCommand handles Google Docs's rate limits automatically so you don't have to throttle manually.
More actions

Other Google Docs actions.

Action
Append Text to Doc
Adds text to the end of a Doc with optional styling. For "daily standup note → append today's update to the weekly notes doc" patterns.
Action
Create Google Doc
Creates a blank Doc. For templated content creation, the standard pattern is Copy a template via Google Drive's Copy File action, then run Replace Text to fill {{placeholders}}.
Action
Replace Text in Doc
Find-and-replace across the doc. The templating workhorse — fill {{customer_name}} placeholders in a templated Doc with workflow data. For multi-replace workflows, batch via Update Document for efficiency.
Action
Update Google Doc (Batch)
Batched-requests API for inserting at specific indexes, formatting ranges, modifying tables. For "insert images at this position" or "format this paragraph as a heading" workflows that go beyond simple text replacement.
Get Google Doc in Google Docs — start free