When to Use It
- Extract content from existing documents for analysis
- Import document content into workflows
- Convert documents to structured data formats
- Analyze document content with AI tools
- Migrate content between platforms
- Create summaries from existing documents
Inputs
Field | Type | Required | Description |
---|---|---|---|
Document | Text | Yes | Google Docs document URL or ID |
Export as Markdown | Toggle | No | Convert content to Markdown format (default: false) |
Document Input Options
URL Format:Export Format Options
Format | Description | When to Use |
---|---|---|
Plain Text | Raw text content with basic structure | Simple text extraction, AI analysis |
Markdown | Formatted text with headers, lists, links, tables | Structured content, web publishing, documentation |
Output
Returns the extracted document content: Plain Text Export:Output Fields:
Field | Description |
---|---|
document_id | Unique Google Docs document ID |
document_title | Title of the document |
content | Extracted text content (plain text or Markdown) |
content_length | Number of characters in the content |
export_format | Format of the exported content |
elements_found | Count of different document elements |
Credit Cost
- Cost per run: 1 credit
Supported Elements
Plain Text Export
- Text content: All paragraph text
- Headings: Converted to text with line breaks
- Lists: Bullet points and numbered lists
- Tables: Tab-separated values
- Links: Link text only (URLs stripped)
Markdown Export
- Headings:
# H1
,## H2
,### H3
, etc. - Lists:
- Bullet points
and1. Numbered lists
- Tables: Markdown table format with
|
separators - Links:
[Link text](URL)
format - Bold/Italic:
**bold**
and*italic*
formatting - Line breaks: Proper Markdown spacing
Common Workflows
Content Analysis:Tips
Format Selection:- Use Plain Text for simple content extraction and AI analysis
- Use Markdown for preserving formatting and structure
- Markdown is better for content that will be republished or reformatted
- Large documents may have significant content - consider processing in chunks
- Check content_length to understand document size before processing
- Use elements_found to understand document structure
- Combine with text processing nodes for content analysis
- Large documents take longer to process
- Markdown export requires more processing than plain text
- Cache results if you need to read the same document multiple times