PDF Fill icon

PDF Fill

Die Node ruft die API PDF Fill auf, die Formulardaten aus PDF extrahiert und Formulare in PDF ausfüllt

Overview

This node interacts with a PDF Fill API to either extract form fields from a PDF document or fill a PDF form with provided data. It is useful in workflows where automated processing of PDF forms is required, such as extracting field names and values for analysis or populating PDF templates with dynamic data before distribution.

Practical examples:

  • Extracting all form fields from a PDF to understand what inputs are required.
  • Automatically filling out a PDF form (e.g., an application or contract) with user data collected elsewhere in the workflow.

Properties

Name Meaning
Base URL The base URL of the PDF Fill API server to which requests will be sent.
Binary Property The name of the binary property containing the PDF file to process.
Password Optional password for password-protected PDF files.

Additional property when operation is Fill (not requested but present in code):

  • Fields: A collection of name-value pairs representing form fields to fill in the PDF.

Output

  • For the Get Fields operation, the output JSON contains a fields property holding the extracted form fields from the PDF.
  • For the Fill operation, the output includes the filled PDF as binary data under the specified binary property (data by default), with MIME type application/pdf.

Dependencies

  • Requires access to a running instance of the PDF Fill API at the specified Base URL.
  • The node sends HTTP POST requests with multipart/form-data payloads including the PDF file and optional parameters.
  • No special credentials are mandated by the node itself, but the API may require authentication depending on deployment.

Troubleshooting

  • Common issues:
    • Incorrect Base URL or unreachable API endpoint will cause HTTP request failures.
    • Providing an incorrect binary property name will result in missing or invalid PDF input.
    • Password-protected PDFs without the correct password may fail to process.
  • Error messages:
    • HTTP errors from the API (e.g., 404, 500) indicate connectivity or server-side problems.
    • Errors related to binary data retrieval suggest misconfiguration of the binary property.
  • Resolutions:
    • Verify the Base URL and ensure the PDF Fill API service is accessible.
    • Confirm the binary property name matches the incoming binary data.
    • Provide the correct password if the PDF is protected.

Links and References

Discussion