Skip to main content
Use google_docs in twins and put this configuration under seed_config.google_docs. Google Docs documents with titled, editable body content.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

Parameters

The following fields belong directly inside seed_config.google_docs. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Seeding behavior

Provision google_docs explicitly to use the Docs API. Drive and Sheets remain separate APIs; selected siblings share file state only within the same Twin Run. Document seeds accept title and content (alias body).

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

documents[]

Typed configuration objects

Named object types in the parameter table use these fields.

ConnectedSheetsConfig

DataSourceResult

DocsGeminiConfig

GeminiResponse

SeedPrincipal

SeedToken

SheetsGeminiConfig

SheetsGeminiResponse

SheetsGeminiAction

API coverage and limitations

Twin name: google_docs CLI quickstart: Use the Google Workspace CLI with Arga twins Supports
  • Google Docs v1 document create, get, and atomic batchUpdate operations.
  • UTF-16 document indexes, text insertion and deletion, replace-all, text and paragraph styling, and named ranges.
  • A Docs v1 Discovery document rewritten to the provisioned twin URL.
  • A browsable Docs-style home and document editor with blank-document creation, autosave, bold, italic, underline, sharing, and document export.
  • The preset document ID google-docs-launch-notes, which matches the corresponding file metadata in the default Drive twin.
Known limitations
  • This provision contains the Docs API and editor UI only. Provision google_drive for Drive metadata and file operations, and google_sheets for spreadsheet editing.
  • The editor focuses on common document workflows. It does not model real-time multi-user cursors, full version history, or every consumer Docs command.
Provision
MCP tools: get_twin_catalog, provision_twins, start_url_validation, get_validation_results. See Scenario seeding for saving, provisioning, and resetting fixtures.