The Text File Reader uses Optical Character Recognition (OCR) to extract raw text content from images, text-based documents, and PDFs. This reader is ideal for simple text extraction when you need to convert visual content into editable text for use in automation workflows.

Key Features

OCR Technology

Advanced optical character recognition extracts text from images and scanned documents

Multi-Format Support

Process PDFs, images (JPG, PNG, TIFF), and text-based documents

Raw Text Extraction

Extracts plain text content without structure analysis

Automation Ready

Seamlessly integrates with automation workflows for document processing

Supported File Types

The Text File Reader can process:

Creating a Text File Reader

1

Navigate to File Readers

In your application, go to File Readers section
2

Create New Reader

Click + File Reader and select Text from the document type options
3

Configure Basic Settings

Name: Enter a descriptive name (e.g., “Contract Text Extraction”)Description: Optional description for team reference
4

Set Up Text Fields

Configure the text fields you want to extract:Field Name: Descriptive name for the extracted text Field Type: Select “Text” for raw text extraction Required: Mark if this field must contain content
5

Test with Sample Document

Upload a sample document to validate text extraction accuracy

Configuration Options

Field Configuration

The Text File Reader extracts content into configurable text fields:
Use Case: Extract all text into one fieldConfiguration:
  • Field Name: “extracted_text”
  • Field Type: Text
  • Description: “Complete document text content”
Best for: Simple text extraction, content analysis

OCR Quality Settings

OCR accuracy depends on document quality. For best results, use high-resolution images and clear text formatting.
Factors affecting OCR accuracy:
  • Image resolution (higher is better)
  • Text clarity and contrast
  • Font size and style
  • Document orientation
  • Background interference

Using in Automations

Integration with Automation Workflows

The Text File Reader integrates seamlessly with automation workflows:
Email Received → Text File Reader → AI Classification → Create Record → Send Notification

Common Automation Patterns

File Reader Action Configuration

When adding a File Reader action to your automation:
  1. Select File Reader Type: Choose your configured Text File Reader
  2. Configure Input Source:
    • File from Email Received trigger
    • Attachment from Record
    • Upload from user interaction
  3. Map Output Fields: Use extracted text in subsequent actions
  4. Handle Errors: Add IF conditions for missing or invalid content

Best Practices

Document Quality

Use high-resolution, clearly formatted documents for best OCR accuracy

Field Validation

Implement validation checks in automations for critical text extraction

Error Handling

Use IF conditions to handle cases where text extraction fails

Performance Optimization

Consider file size limits and processing time for large documents

Document Preparation Tips

For Best OCR Results:
  • Use documents with clear, dark text on light backgrounds
  • Ensure proper orientation (not rotated or tilted)
  • Avoid documents with heavy background patterns
  • Use standard fonts when possible
  • Maintain good contrast between text and background
File Size Considerations:
  • Optimize image resolution (300 DPI is typically sufficient)
  • Balance quality with processing time
  • Consider splitting large documents into smaller sections

Advanced Features

Text Post-Processing

After OCR extraction, you can enhance the text using automation actions:
1

Transform Data with AI

Clean and normalize extracted text, fix common OCR errors
2

AI Classification

Categorize extracted content based on text analysis
3

AI Summarization

Create concise summaries of lengthy extracted text

Batch Processing

Process multiple documents efficiently:
File Upload → Repeat For Each → Text File Reader → Transform Data → Update Records
Configuration:
  1. Set up trigger for multiple file uploads
  2. Use Repeat For Each to iterate through files
  3. Apply Text File Reader to each document
  4. Process extracted text with subsequent actions

Error Handling and Troubleshooting

Common Issues

Validation and Testing

Always test your Text File Reader with representative sample documents before deploying in production automations.
Testing Process:
  1. Upload sample documents similar to production files
  2. Review extracted text for accuracy
  3. Test with different document qualities and formats
  4. Validate field mapping and data types
  5. Test error handling with problematic documents

Comparison with Other File Readers

When to Use Text File Reader

Choose Text File Reader when:
  • You need simple text extraction without structure
  • Processing scanned documents or images
  • Working with various document formats
  • OCR accuracy is sufficient for your use case
Consider alternatives when:

Performance Comparison

FeatureText File ReaderElementum IntelligencePurchase Orders
Speed⭐⭐⭐⭐⭐⭐⭐⭐⭐
Accuracy⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐
Flexibility⭐⭐⭐⭐⭐⭐⭐⭐⭐
Cost⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐

Integration Examples

Email Processing Workflow

Email Received (with attachment) → Text File Reader → AI Classification → Create Support Ticket
Configuration:
  1. Trigger: Email Received
  2. File Reader: Extract text from email attachment
  3. AI Classification: Categorize issue type
  4. Create Record: Generate support ticket with extracted text
  5. Send Email: Confirm receipt and ticket number

Document Archival System

Document Upload → Text File Reader → Transform Data → Update Record → Generate Report
Configuration:
  1. Trigger: Attachment Added
  2. File Reader: Extract text content
  3. Transform Data: Clean and standardize text
  4. Update Record: Store extracted content for search
  5. Generate Report: Create searchable document index

Next Steps


The Text File Reader provides reliable OCR-based text extraction for a wide variety of document types. Use it for simple text extraction needs or as a foundation for more complex document processing workflows.