Saving Google Docs

DocsAutomator lets you save Google Docs in addition to PDF, so you can continue editing even after generation

Overview

DocsAutomator enables you to preserve Google Docs after generation for continued editing, complementing PDF export functionality. Google Docs are saved as editable documents in your Google Drive, allowing you to make changes even after the initial generation.

DocsAutomator's Save Google Doc? Feature

Optionally, you can set the "Google Doc Destination Folder" which determines where the Google Doc will be stored in your Google Drive.

Sharing / visibility settings

Stored Google Docs inherit sharing options from their parent folder. Example: If the folder is publicly shared, view only, the stored Google Doc will have the same sharing settings.

Save Google Doc in Airtable

If you're using Airtable as your data source, enabling "Save Google Doc?" will show an additional field in the Airtable mapping section:

Save Google Doc Link in Airtable

This allows you to pick a field in Airtable where the link to the Google will be stored.

Save Google Doc via the API

If you're using DocsAutomator's API, the API response will include an additional key "googleDocUrl" with the link to the Google Doc as its value. See DocsAutomator API for more.

Dynamic Subfolder Creation

DocsAutomator now supports automatic generation of nested folder structures using both static text and dynamic placeholders. This powerful feature allows you to organize your Google Docs based on your document data.

How It Works

When you select a Google Drive destination folder, you'll see an optional "Subfolder Name" field that allows you to create dynamic folder structures within your chosen folder.

Using Static Text

Create simple, static folder hierarchies:

• Reports

• Invoices

• 2024/Q1

• Contracts/Signed

Using Placeholders

Leverage your document data to create dynamic folder structures:

Basic Examples:

• {{client_name}} - Creates a folder named after the client

• {{date}}_Documents - Creates folders like "2024-01-19_Documents"

• {{year}}/{{month}} - Creates nested folders like "2024/January"

Advanced Examples:

• Clients/{{client_name}}/{{year}} - Multi-level organization

• {{department}}/{{project_name}} - Department-based structure

• {{status}}/{{date}} - Organize by status and date

Adding Placeholders

Quick Method: Type / in the subfolder name field to browse and select from available placeholders.

Manual Method: Enter placeholders using the {{placeholder_name}} format directly.

How Nested Folders Work

• Path Separator: Use forward slashes (/) to create nested folder structures

• Automatic Creation: Folders are created automatically if they don't exist

• Folder Reuse: If a folder already exists, documents are placed in the existing folder (no duplicates created)

• Multiple Levels: You can create as many nested levels as needed

Example: If you specify Clients/{{client_name}}/{{year}} and the client name is "Acme Corp" with year "2024", the system will:

1. Check if "Clients" folder exists (create if not)

2. Check if "Acme Corp" folder exists inside "Clients" (create if not)

3. Check if "2024" folder exists inside "Acme Corp" (create if not)

4. Save the Google Doc in the final folder

Important Limitations

Line Item Placeholders

Line item placeholders (fields that contain multiple rows of data) cannot be used in subfolder names. Only single-value fields are supported.

Empty Placeholder Values

If a placeholder has no value:

• The placeholder is removed from the folder path

• Empty path segments are cleaned up

• The document saves to the main selected folder (or the closest valid parent folder)

Example: If you specify {{department}}/{{project}} but department is empty, the document will save directly in {{project}} folder.