Actions80
- Extract Text From Word
- Find And Replace Text
- Convert PDF To Editable PDF Using OCR
- Create Swiss QR Bill
- Split PDF By Barcode
- Split PDF By Swiss QR
- Split PDF By Text
- Split PDF Regular
- Create PDF/A
- Convert HTML To PDF
- Convert Markdown To PDF
- Upload File To PDF4me
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Fill PDF Form
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- AI-Invoice Parser
- AI-Process HealthCard
- AI-Process Contract
- Generate Barcode
- Classify Document
- Parse Document
- Linearize PDF
- Flatten PDF
- Convert To PDF
- Json To Excel
- Convert PDF To Excel
- Convert PDF To Word
- Convert PDF To PowerPoint
- Convert VISIO
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Extract Pages
- Merge Multiple PDFs
- Overlay PDFs
- Rotate Document
- Rotate Page
- Sign PDF
- URL to PDF
- Add Image Watermark To Image
- Add Text Watermark To Image
- Compress Image
- Convert Image Format
- Create Images From PDF
- Flip Image
- Get Image Metadata
- Image Extract Text
- Remove EXIF Tags From Image
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Image
- Rotate Image By EXIF Data
- Compress PDF
- Get PDF Metadata
- Repair PDF Document
- Get Document From Pdf4me
- Update Hyperlinks Annotation
- Protect Document
- Unlock PDF
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Generate Document Single
- Generate Documents Multiple
- Get Tracking Changes In Word
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Attachment From PDF
- Extract Text By Expression
- Extract Table From PDF
- Extract Resources
Overview
The node provides an AI-powered invoice parsing operation that extracts structured data from invoice documents. It supports multiple input methods for the invoice file, including binary data from a previous node, a base64-encoded string, or a URL pointing to the invoice file.
This node is beneficial in automating accounts payable workflows, expense management, and financial data entry by converting unstructured invoice files into structured JSON data. For example, it can be used to automatically extract vendor details, invoice numbers, dates, line items, and totals from PDF invoices without manual data entry.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | Choose how to provide the invoice document to process. Options: Binary Data, Base64 String, URL |
| Input Binary Field | (If using Binary Data) The name of the binary property containing the invoice file |
| Base64 Invoice Content | (If using Base64 String) The base64 encoded content of the invoice document |
| Invoice URL | (If using URL) The URL pointing to the invoice file to process |
| Invoice Name | The name of the source invoice file for reference (e.g., "invoice.pdf") |
Output
The node outputs JSON data representing the parsed invoice information extracted by the AI parser. This typically includes fields such as invoice number, date, vendor details, line items, amounts, taxes, and totals in a structured format suitable for further processing or storage.
If the input was provided as binary data or URL, the output JSON will contain the parsed invoice data corresponding to that input. There is no indication that the node outputs binary data itself.
Dependencies
- Requires access to an AI-powered invoice parsing service (likely via an API).
- Needs appropriate API authentication credentials configured in n8n to connect to the external invoice parsing service.
- Internet connectivity is required if providing invoice files via URL or if the parsing service is cloud-based.
Troubleshooting
Common Issues:
- Providing an incorrect binary property name when using binary data input may cause the node to fail to find the invoice file.
- Invalid or inaccessible URLs will result in errors fetching the invoice file.
- Malformed base64 strings will cause decoding failures.
- Unsupported invoice file formats or corrupted files may lead to parsing errors.
Error Messages:
- Errors related to missing or invalid input data usually indicate misconfiguration of the input properties.
- Authentication errors suggest issues with the API key or credential setup.
- Network errors imply connectivity problems or invalid URLs.
Resolutions:
- Verify the binary property name matches the actual binary field from the previous node.
- Ensure URLs are accessible and point directly to the invoice file.
- Validate base64 strings before input.
- Confirm API credentials are correctly set up and have necessary permissions.