Actions80
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Image Watermark To Image
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- Add Text Watermark To Image
- AI-Invoice Parser
- AI-Process Contract
- AI-Process HealthCard
- Classify Document
- Compress Image
- Compress PDF
- Convert HTML To PDF
- Convert Image Format
- Convert JSON To Excel
- Convert Markdown To PDF
- Convert PDF To Editable PDF Using OCR
- Convert PDF To Excel
- Convert PDF To PowerPoint
- Convert PDF To Word
- Convert To PDF
- Convert URL to PDF
- Convert VISIO
- Convert Word to PDF Form
- Create Images From PDF
- Create PDF/A
- Create Swiss QR Bill
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Extract Attachment From PDF
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Resources
- Extract Table From PDF
- Extract Text By Expression
- Extract Text From Word
- Fill PDF Form
- Find And Replace Text
- Flip Image
- Flatten PDF
- Generate Barcode
- Generate Document Single
- Generate Documents Multiple
- Get Document From Pdf4me
- Get Image Metadata
- Get PDF Metadata
- Get Tracking Changes In Word
- Image Extract Text
- Linearize PDF
- Merge Multiple PDFs
- Overlay PDFs
- Parse Document
- Protect PDF
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Remove EXIF Tags From Image
- Repair PDF Document
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Document
- Rotate Image
- Rotate Image By EXIF Data
- Rotate PDF Page
- Sign PDF
- Split PDF By Barcode
- Split PDF By Swiss QR
- Split PDF By Text
- Split PDF Regular
- Unlock PDF
- Update Hyperlinks Annotation
- Upload File To PDF4me
Overview
The node provides an AI-powered contract processing operation within a PDF/document automation workflow. It accepts a contract document in various input formats (binary data, base64 string, or URL) and processes it using AI capabilities to extract meaningful information or perform contract-specific analysis.
This node is beneficial for automating contract review, extraction of key terms, compliance checks, or integration into larger document management workflows. For example, a user can feed scanned contracts or digital contract files to automatically parse clauses, dates, parties involved, or other structured data without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | Choose how to provide the contract document to process. Options: Binary Data, Base64 String, URL |
| Input Binary Field | Name of the binary property containing the contract file (used if Input Data Type is Binary Data) |
| Base64 Contract Content | Base64 encoded content of the contract document (used if Input Data Type is Base64 String) |
| Contract URL | URL pointing to the contract file to process (used if Input Data Type is URL) |
| Contract Name | Name of the source contract file for reference (e.g., original-contract.pdf) |
Output
The node outputs JSON data representing the results of the AI contract processing. This typically includes extracted contract details, metadata, or analysis results depending on the AI model's capabilities.
If the input was binary or URL-based, the output JSON will contain structured data derived from the contract content. The node does not explicitly output binary data itself but processes input binary or encoded content internally.
Dependencies
- Requires access to an external AI-powered contract processing service or API.
- Needs proper authentication configured in n8n to connect to this service (e.g., an API key credential).
- Internet connectivity is required if providing contract files via URL or if the AI processing happens remotely.
Troubleshooting
Common Issues:
- Incorrect input data type selection leading to missing or invalid contract content.
- Invalid or inaccessible URLs when using the URL input option.
- Malformed base64 strings causing decoding errors.
- Missing or incorrect binary property name when using binary input.
- Authentication failures due to misconfigured API credentials.
Error Messages & Resolutions:
- "Failed to fetch contract file from URL": Check URL accessibility and correctness.
- "Invalid base64 content": Verify that the base64 string is properly encoded and complete.
- "Binary property not found": Ensure the binary field name matches the actual binary data property from previous nodes.
- "Authentication error": Confirm API key or token is correctly set up in n8n credentials.
- "AI processing failed": Review service status and input data validity; retry or contact support if persistent.
Links and References
- n8n Documentation
- Relevant AI contract processing service documentation (not specified here)
- General info on base64 encoding: https://en.wikipedia.org/wiki/Base64
- Best practices for handling binary data in n8n: https://docs.n8n.io/nodes/working-with-binary-data/