n8n-nodes-edocument

An n8n community node for eDocument OCR API that allows you to extract text from images with Vietnamese language support and automatic credential management.

!n8n.io - Workflow Automation

✨ New Features v1.1.0

- 🤖 Auto-Generated Credentials: Automatically generate and share API keys across workflow steps
- 🔄 Smart Credential Reuse: Once generated, credentials are shared across all eDocument OCR nodes in the same workflow
- 🛡️ Automatic Key Validation: Auto-regenerate expired keys transparently
- 🎯 Simple Trigger: Works seamlessly with previous node outputs as inputs

Features

- Auto-Credential Management: No more manual API key setup - just add the node and go!
- Dual OCR Processing: Choose between fast processing for typed text or advanced processing for handwritten text
- Vietnamese Language Optimized: Specially designed for Vietnamese text recognition
- Multiple Input Methods: Support for binary data and URL-based image processing
- Rich Output Options: Extract text with optional confidence scores and coordinates
- Error Handling: Comprehensive error handling with automatic retry and quota management

Installation

To install this community node in n8n:

1. Go to Settings > Community Nodes
2. Select Install
3. Enter n8n-nodes-edocument in the Enter npm package name field
4. Agree to the risks and select Install

Usage

$3

1. Add the eDocument OCR node to your workflow
2. Connect it to any previous node (the output becomes the input automatically)
3. Select "Auto-generated (Shared)" credential mode (default)
4. Configure your OCR settings and run!

The node will automatically:
- Generate a free API key (100 requests) on first use
- Share this key across all eDocument OCR nodes in the same workflow
- Handle key validation and regeneration transparently

$3

#### 🤖 Auto-Generated (Shared) - Recommended
``
Previous Node → eDocument OCR (Auto-mode) → Next Node
↓
Automatically generates & shares API key
`

- First use: Automatically calls API to generate a new key
- Subsequent uses: Reuses the same key across all eDocument nodes in workflow
- Key expiry: Automatically regenerates expired keys
- No setup required: Just add the node and run

#### 🔧 Manual Credentials - Traditional
`
Previous Node → eDocument OCR (Manual mode) → Next Node
↓
Uses manually configured credentials
`

- Create credentials of type eDocument API
- Enter your API key manually
- Use when you have your own API key or need specific control

$3

#### OCR Types

- Fast OCR (Typed Text Only): High-speed processing ideal for printed documents, forms, and typed text
- Advanced OCR (Handwritten Text): More comprehensive processing that can handle handwritten text, but slower

#### Input Methods

- Binary File: Use image data from previous nodes (most common)
- URL: Process images directly from web URLs

#### Options

- Return Confidence Score: Get accuracy confidence for extracted text
- Return Coordinates: Receive position data for detected text regions

$3

#### Basic Auto-Credential Workflow
`
HTTP Request (Get Image) → eDocument OCR (Auto-mode) → Process Results
`

#### Batch Processing with Shared Credentials
`
Google Drive (Get Files) → eDocument OCR (Auto-mode) → eDocument OCR (Auto-mode) → Google Sheets
↓________________________↑
Same auto-generated key shared automatically
`

#### Multi-Step OCR Processing
`
Webhook → eDocument OCR (Fast, Auto) → eDocument OCR (Advanced, Auto) → Email Results
↓_________________________________↑
Same API key automatically shared
`

Auto-Credential Benefits

$3

- Zero setup: No need to understand API keys or credentials
- Instant start: Add node → Configure → Run
- 100 free requests: Automatically included with each key generation

$3

- Simplified workflows: No more credential management across multiple nodes
- Automatic recovery: Expired keys are regenerated transparently
- Backward compatible: Manual credential mode still available

$3

- Consistent behavior: Same credential management across all team workflows
- Reduced errors: No more "invalid API key" issues from manual entry
- Easy scaling: Add more OCR nodes without credential setup

Testing

Test the auto-generation functionality:

`bash
npm run test-api-generation
``

This will:
1. Generate a new API key using your API
2. Validate the generated key
3. Report success/failure

API Limits

- Auto-Generated Keys: 100 requests per generated key
- Manual Keys: Based on your plan
- Key Sharing: All nodes in the same workflow share the same auto-generated key
- Regeneration: Automatic when keys expire (transparent to user)

Migration Guide

$3

Existing workflows continue to work unchanged.

To use auto-generation in existing workflows:
1. Edit your eDocument OCR nodes
2. Change "Credential Mode" from "Manual Credentials" to "Auto-generated (Shared)"
3. Save and run

Your old manual credentials remain available if you want to switch back.

Troubleshooting

$3

Problem: "Your eDocument API key has expired!"
Solutions:
1. Purchase new credits: Visit e-doc-pay.eranin.com
2. For auto-generated keys: After purchase, enable "Force New Key Generation" option
3. For manual keys: Update your credentials with the new API key
4. Alternative: Switch to auto-mode for a new free key (100 requests)

$3

Problem: "Failed to auto-generate API key"
Solution:
1. Check internet connectivity
2. Try switching to manual credential mode temporarily
3. Verify the API endpoint is accessible

Problem: "API quota exceeded"
Solution:
1. Purchase additional credits at e-doc-pay.eranin.com
2. Update your credentials or force new key generation

$3

Problem: "No API key provided"
Solution:
1. Create eDocument API credentials in n8n
2. Or switch to auto-generated mode

Support

- Documentation: https://e-doc-api.eranin.com
- Issues: GitHub Issues
- Email Support: support@eranin-tech.com
- Purchase Credits: e-doc-pay.eranin.com

License

MIT © Eranin.com

---

Note: This is a community-maintained package. For official n8n nodes, visit n8n.io.