Append Text to Doc: Google Docs action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Document ID documentId	string	Required	Document ID. Example: 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms
Text to Append text	string	Required	Text to Append

Sample request

{
  "documentId": "e.g. 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms",
  "text": "{{trigger.text}}"
}

Returns

{
  "replies": [
    {}
  ],
  "documentId": "1BxiMVs0..."
}

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

FAQ

Questions about Append Text to Doc.

What does the Append Text to Doc action do in Google Docs?

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.

What inputs does Append Text to Doc require?

Required: Document ID, Text to Append. 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 Append Text to Doc support batch operations?

Yes. Run Append Text to Doc inside a Loop node to process arrays. Tiny Command handles Google Docs's rate limits automatically so you don't have to throttle manually.

More actions