Skip to main content

Open Document

Opens an existing Google Docs document.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

  • URL - The URL of the Google Docs document to open.

Output​

  • Document Id - The ID of the opened Google Docs document.

Options​

  • Credentials - Google Docs credentials used to authenticate with the service.

How It Works​

The Open Document node integrates with Google Docs to open an existing document. When executed, the node:

  1. Validates the provided inputs (URL)
  2. Authenticates with Google Docs using the provided credentials
  3. Opens the Google Docs document specified by the URL
  4. Returns the document ID of the opened document

Requirements​

  • Valid Google Docs credentials
  • A valid URL of an existing Google Docs document
  • Proper permissions to access the document

Error Handling​

The node will return specific errors in the following cases:

  • Empty or invalid URL
  • Empty or invalid Google Docs credentials
  • Google Docs service errors
  • Insufficient permissions to access the document

Usage Notes​

  • The URL input should be the full URL of the Google Docs document
  • The Document Id output can be used in subsequent nodes to modify the document
  • The node requires appropriate permissions to access the specified document
  • The opened document will be accessible through the document ID in subsequent nodes
  • This node is useful for working with existing documents rather than creating new ones

Practical Examples​

Example 1: Open a Document by URL​

Open an existing document using its URL:

Inputs:

  • URL: "https://docs.google.com/document/d/1ABCdefGHIjklMNOpqrSTUVwxyz123456/edit"

Result: Document is opened and ID is stored in $.document_id for use in subsequent nodes

Example 2: Open Document from Data Table​

Open documents listed in a data table for batch processing:

Inputs:

  • URL: $.row.document_url (from For Each loop over data table)

Use Case: Process multiple documents in a loop, applying the same updates to each

Example 3: Open Template Document​

Open a template document to read its structure:

Inputs:

  • URL: "https://docs.google.com/document/d/template-doc-id/edit"

Next Steps: Use Read Document to extract template structure, then create new documents based on it

Example 4: Update Shared Document​

Open a shared document for automated updates:

Inputs:

  • URL: $.config.weekly_report_url (stored in configuration)

Use Case: Update a weekly report document every Monday with new data

Example 5: Using Document ID Instead of URL​

If you only have the document ID:

Inputs:

  • URL: "https://docs.google.com/document/d/" + $.doc_id + "/edit" (construct URL from ID)

Note: The node extracts the ID from the URL, so constructing a full URL from just the ID works fine

Tips for Effective Use​

  1. Extract ID from URL - The node automatically extracts the document ID from the URL
  2. Reuse connections - Once opened, the document stays accessible via its ID throughout the flow
  3. Check permissions - Ensure the account has at least "view" access to the document
  4. Share with service account - If using service account auth, share the document with the service account email
  5. Store URLs centrally - Keep document URLs in config, vault, or data tables for easy management
  6. Handle invalid URLs - Use Try-Catch to handle cases where URL might be invalid
  7. Use for existing content - This is the starting point for reading or modifying existing documents

Common Errors and Solutions​

Error: "Invalid Google Document Url"​

Cause: URL format is incorrect or not a valid Google Docs URL

Solution:

  • Verify the URL starts with https://docs.google.com/document/d/
  • Ensure URL contains the document ID
  • Copy URL directly from browser address bar
  • Correct format: https://docs.google.com/document/d/{DOCUMENT_ID}/edit

Error: "No Credential Content"​

Cause: Credentials are not configured or missing

Solution:

  • Select credentials in the Options
  • Verify OAuth2 or Service Account credentials are set up
  • Re-authenticate if using OAuth2

Error: "ErrAuth" - Authentication failed​

Cause: Invalid credentials or expired OAuth2 token

Solution:

  • For OAuth2: Re-authorize by running the flow
  • For Service Account: Verify JSON key is correct
  • Check Google Docs API is enabled in Cloud Console

Error: "URL cannot be empty"​

Cause: URL input is empty or variable doesn't contain a value

Solution:

  • Check that URL variable has a value
  • Verify data source contains valid URLs
  • Add validation before Open Document node

Error: Permission denied / Document not accessible​

Cause: Account doesn't have access to the document

Solution:

  • For OAuth2: Document must be in your Google Drive or shared with you
  • For Service Account: Share document with service account email (found in JSON key under "client_email")
  • Verify document hasn't been deleted or URL is correct
  • Check document isn't restricted by organization policies

Error: Document not found​

Cause: Document was deleted or URL is incorrect

Solution:

  • Verify document exists by opening URL in browser
  • Check for typos in document ID
  • Ensure document wasn't moved to trash

Integration Patterns​

Pattern 1: Batch Document Processing​

Process multiple documents from a list:

1. Read document URLs from Data Table
   ↓
2. For Each URL
   ↓
3. Open Document (URL from loop)
   ↓
4. Read/Modify document content
   ↓
5. Continue to next document

Pattern 2: Scheduled Document Updates​

Update a document on a schedule:

1. Trigger (scheduled daily/weekly)
   ↓
2. Open Document (URL from config)
   ↓
3. Insert Text or Replace Text with new data
   ↓
4. PDF Export (optional)

Pattern 3: Document Content Extraction​

Extract data from multiple documents:

1. Open Document
   ↓
2. Read Document (get all text)
   ↓
3. Parse/Process content (use JavaScript or other nodes)
   ↓
4. Store results in Data Table

Pattern 4: Template-based Document Update​

Update template with dynamic content:

1. Open Document (template URL)
   ↓
2. Replace Text (replace {{placeholders}} with actual values)
   ↓
3. PDF Export or share updated document

URL Formats Supported​

Valid Google Docs URL formats that work with this node:

  • Standard edit URL: https://docs.google.com/document/d/DOCUMENT_ID/edit
  • URL with parameters: https://docs.google.com/document/d/DOCUMENT_ID/edit?usp=sharing
  • URL with section: https://docs.google.com/document/d/DOCUMENT_ID/edit#heading=h.abc123

Note: The node extracts the document ID automatically from any of these formats.