Parse PDF
AI-generatedOverview
This node integrates with the LandingAI agentic document analysis API to parse PDF documents. It accepts a PDF file as binary input and sends it to the LandingAI service, which performs advanced document parsing and returns structured data extracted from the PDF content.
Common scenarios for this node include:
- Automating extraction of text, tables, or form data from scanned or digital PDF documents.
- Processing invoices, receipts, contracts, or reports to convert them into machine-readable JSON.
- Integrating document parsing into workflows that require automated data ingestion from PDFs.
For example, you could use this node after a file upload trigger to automatically extract invoice details from uploaded PDFs and then route the data to an accounting system.
Properties
| Name | Meaning |
|---|---|
| Binary Property Name | The name of the binary property containing the PDF file to be parsed. Commonly "data" or "data0". |
Output
The node outputs a JSON object representing the parsed content returned by the LandingAI agentic document analysis API. This JSON typically contains structured information extracted from the PDF, such as recognized text blocks, tables, fields, or metadata depending on the API's response format.
If the node encounters an error during processing and "Continue On Fail" is enabled, it outputs a JSON object with an error field describing the issue.
The node does not output any binary data.
Dependencies
- Requires an active LandingAI API key credential configured in n8n for authentication.
- Makes HTTP POST requests to the LandingAI agentic document analysis endpoint at
https://api.va.dev.landing.ai/v1/tools/agentic-document-analysis. - Expects the input PDF file to be provided as binary data within the specified binary property.
Troubleshooting
- No binary data found: If the specified binary property does not exist or the input item lacks binary data, the node will throw an error indicating missing binary data. Ensure the input contains the PDF file in the correct binary property.
- File is not a PDF: The node validates that the binary data has a MIME type including "pdf". If not, it throws an error. Verify that the input file is indeed a PDF.
- API errors: Network issues or invalid API credentials can cause request failures. Check your LandingAI API key configuration and network connectivity.
- Parsing errors: If the API returns unexpected data or the response cannot be parsed as JSON, the raw response is included in the output for debugging.
Enabling "Continue On Fail" allows the workflow to proceed even if some items fail, with error details included in the output.
Links and References
- LandingAI Agentic Document Analysis API Documentation (Please refer to official LandingAI resources for detailed API usage)
- n8n Documentation - Working with Binary Data
- n8n Documentation - HTTP Request Node