Google Docs Tool

The Google Docs Tool allows DinoAI to import and read content from Google Docs, bringing your specifications, requirements, and documentation directly into your development workflow.

This tool bridges the gap between planning and implementation, enabling DinoAI to extract structured content from Google Docs and turn it into actionable development work β€” from dbt model requirements to implementation steps.

plug-circle-plus

Requires Google Docs integration. Before using this tool, make sure you've connected your Google account in Paradime. See Connecting Google Docs to Paradime for setup instructions.

Capabilities

The read_google_doc tool extracts the full content of a Google Doc and converts it into a format DinoAI can reason over and act on. Specifically, it:

  • Converts Google Docs to clean markdown

  • Preserves headings, lists, tables, links, and inline styling

  • Includes document metadata such as title and last modified date

  • Handles complex formatting structures

Using the Google Docs Tool

  1. Open DinoAI in the right panel of the Code IDE

  2. Provide the Google Doc ID or URL you want to reference (e.g., 1abc...xyz or a full Google Docs URL)

  3. Add your prompt describing what you want DinoAI to do with the document content

  4. Grant permission when DinoAI asks to access the document

  5. Review and implement DinoAI's suggested actions

Example Use Cases

Turning a Spec into Implementation Steps

Prompt

Result: DinoAI extracts the document content, identifies key requirements, and breaks them down into a sequenced list of development tasks you can work through directly in the IDE.

Generating dbt Model Requirements

Prompt

Result: DinoAI reads the specification, identifies the relevant data entities and business logic, and suggests the appropriate dbt models, sources, and test definitions to implement.

Working with Other Tools

The Google Docs Tool works well alongside DinoAI's other capabilities to support your full development workflow:

  • Combine with the Terminal Tool to scaffold models and run dbt commands based on spec requirements

  • Combine with the Linear Tool or Jira Tool to cross-reference ticket requirements against a linked Google Doc

  • Use alongside Git Lite to commit and push your changes before creating a pull request

Best Practices

  • Share the doc correctly β€” Ensure the Google Doc is accessible to the account connected in Paradime

  • Use well-structured docs β€” DinoAI works best with documents that use clear headings, lists, and sections rather than large blocks of unformatted text

  • Be specific in your prompt β€” Tell DinoAI exactly what you want extracted or produced, such as model names, test types, or implementation order

  • Verify the output β€” Always review DinoAI's interpretation of your document before implementing, especially for complex or ambiguous specifications

Last updated

Was this helpful?