ClawTrust
5.8k Downloads
Overview
Provide a managed OAuth gateway to the Google Docs API so the assistant can create, read, and modify Google Docs documents via HTTP requests without handling raw Google OAuth flows directly.
Key Advantages
1.Managed OAuth: offloads Google OAuth connection management to Maton (ctrl.maton.ai), avoiding manual token handling in the skill or agent.
2.Full Docs API surface: the gateway proxies directly to docs.googleapis.com, allowing access to essentially the full Google Docs API (documents.get, documents.create, documents.batchUpdate, etc.).
3.Clear HTTP pattern: simple, consistent REST interface via https://gateway.maton.ai/google-docs/{native-api-path} with standard JSON payloads.
4.Good examples: provides concrete Python and JavaScript snippets for creating documents, inserting text, batchUpdate operations, and managing connections.
5.Connection selection: supports multiple Google Docs accounts via the Maton-Connection header, enabling multi-account workflows in one agent environment.
Use Cases
- Generate new Google Docs files from user prompts (e.g., draft reports, meeting notes, summaries).
- Programmatically edit existing documents: insert text, delete ranges, replace placeholders, update styles.
- Template-based workflows: use replaceAllText for placeholder-based templating (e.g., proposals, invoices, contracts).
- Structured content creation: insert tables, apply formatting, and layout (page breaks, styles) in automated document-generation pipelines.
- Multi-user or multi-account setups where the assistant must operate on different users’ Google Docs via separate OAuth connections.
Evaluation Scores
7.7
/ 10
Reliability
7.5
Functionality
8.0
Usability
7.5
Safety
7.0
Performance
8.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: darwin-arm64LLM: anthropic/claude-sonnet-4.6
**Quick judgment**
A solid, general-purpose Google Docs integration that exposes the full Docs API via a managed OAuth gateway. Best suited for agents that need to create and programmatically edit Google Docs, especially in production-like setups where you don’t want to manage raw Google OAuth tokens yourself.
**Strengths**
- Uses a stable HTTP+JSON pattern that closely mirrors the native Google Docs API.
- Managed OAuth via Maton simplifies connection setup and rotation, including multi-account support.
- Good coverage for core operations (create documents, batchUpdate for text insertion, deletion, placeholders, styles, tables, page breaks).
- Clear error semantics and troubleshooting guidance for API key and connection issues.
**Key risks / limitations**
- Hard dependency on Maton’s gateway and control plane: if maton.ai or ctrl.maton.ai are down or change behavior, the skill fails even if Google’s API is up.
- Requires an external MATON_API_KEY and an established Google Docs OAuth connection; initial setup is non-trivial for end users.
- No high-level abstractions: the agent must understand Docs API details (indices, ranges, field masks, document structure) to avoid incorrect edits.
- Data passes through a third-party gateway, which may be a concern for sensitive or regulated documents (privacy/compliance risk).
- Rate limits (10 req/sec/account) may be constraining for very high throughput use.
**Recommended scenarios**
- Assistants that need **reliable, repeatable document generation** in Google Docs (reports, briefs, specs, meeting notes) with formatting control.
- **Template-based workflows** where placeholders in existing Docs are programmatically filled (e.g., client proposals, contracts, invoices).
- Tools that must operate across **multiple Google accounts** while centralizing OAuth and API key management via Maton.
- Developer-oriented environments where the builder is comfortable working with the raw Google Docs API model (ranges, batchUpdate, field masks) and wants a straightforward HTTP gateway rather than implementing OAuth themselves.
Comments (0)
No comments yet. Be the first!