When to Use It
- Start new document projects from scratch
- Generate documents automatically as part of workflows
- Create template documents for recurring reports
- Initialize documents that will be populated by other nodes
- Build automated document generation pipelines
- Set up documents for content workflows
Inputs
Field | Type | Required | Description |
---|---|---|---|
Connection | Connection | Yes | Your Google Drive connection |
Document Name | Text | Yes | The name of the new Google Docs document to create |
Document Naming Tips
Good naming practices:- Use descriptive names: “Weekly Status Report”, “Project Proposal”
- Include dates or versions: “Meeting Notes - October 2024”
- Follow your organization’s naming conventions
- Avoid special characters that might cause issues
Monthly Report - {current_month}
Client Proposal - {client_name}
Meeting Minutes - {meeting_date}
Project Documentation
Output
Returns the details of the newly created document:Output Fields:
Field | Description |
---|---|
document_id | Unique Google Docs document ID |
document_name | Name of the created document |
document_url | Direct link to edit the document |
created_time | When the document was created |
Credit Cost
- Cost per run: 1 credit
Common Workflows
Automated Report Generation:Tips
- Use descriptive names to easily identify documents later
- Create documents at the start of your workflow, then populate with other nodes
- Combine with other Docs nodes to build complete document workflows
- Include timestamps or dates in names for recurring reports