PDF4me icon

PDF4me

Comprehensive PDF and document processing: generate barcodes, convert files, extract data, manipulate images, and automate workflows with the PDF4ME API

Actions80

Overview

This node extracts form data from a PDF document. It is useful when you need to programmatically retrieve filled-in form values from PDF files, such as surveys, applications, contracts, or any PDF with interactive form fields. The node supports multiple input methods for the PDF file: binary data from a previous node, a base64 encoded string, or a URL pointing to the PDF.

Practical examples:

  • Automatically extracting user-submitted data from PDF forms uploaded via a web form.
  • Processing PDF invoices or contracts to extract key information without manual data entry.
  • Integrating with document management systems to parse and index form data from stored PDFs.

Properties

Name Meaning
Input Data Type Choose how to provide the PDF file:
- Binary Data (from previous node)
- Base64 String
- URL
Input Binary Field Name of the binary property containing the PDF file (default "data"). Used only if Input Data Type is Binary Data
Base64 PDF Content Base64 encoded content of the PDF document. Used only if Input Data Type is Base64 String
PDF URL URL to the PDF file to extract form data from. Used only if Input Data Type is URL
Document Name Name of the document used during processing (default "document.pdf")
Advanced Options Custom JSON profiles to adjust API call properties, e.g., setting output data format or other specific options

Output

The node outputs an array of JSON objects representing the extracted form data from the PDF. Each object corresponds to one input item processed and contains the parsed form field names and their respective values.

If the PDF contains binary data or attachments, those are not part of this output; the focus is strictly on form data extraction.

Dependencies

  • Requires access to an external PDF processing API service that supports form data extraction.
  • Needs proper API authentication configured in n8n (e.g., an API key credential).
  • Internet access may be required if providing a PDF URL.

Troubleshooting

  • Common issues:
    • Providing an incorrect binary property name will cause the node to fail to find the PDF file.
    • Invalid base64 strings or inaccessible URLs will result in errors.
    • If the PDF does not contain any form fields, the output will be empty or minimal.
  • Error messages:
    • Errors related to missing or invalid input data usually indicate misconfiguration of input properties.
    • API errors might occur due to authentication failure or exceeding usage limits.
  • Resolutions:
    • Verify the binary property name matches the actual binary data field.
    • Ensure base64 content is correctly encoded and complete.
    • Confirm the URL is accessible and points directly to a valid PDF file.
    • Check API credentials and permissions.

Links and References

Discussion