PDF Fill
Die Node ruft die API PDF Fill auf, die Formulardaten aus PDF extrahiert und Formulare in PDF ausfüllt
Actions2
Overview
This node integrates with a PDF Fill API to either fill PDF forms with provided data or extract form fields from PDF files. It is useful in workflows where automated processing of PDF forms is required, such as populating standardized documents (e.g., contracts, applications) with user data or extracting field information for validation or analysis.
Practical examples:
- Automatically filling a PDF application form with customer details collected from a web form.
- Extracting all form field names and types from a PDF template to dynamically generate input forms in an application.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the PDF Fill API service to which requests are sent. |
| Binary Property | The name of the binary property containing the PDF file to process. |
| Password | Optional password for password-protected PDF files. |
| Fields | A collection of fields to fill in the PDF when using the "Fill" operation. Each field has: |
| - Name | The name of the form field in the PDF. |
| - Value | The value to fill into the corresponding form field. |
Output
- For the Fill operation: Outputs the filled PDF as binary data under the binary property named
data. The JSON part of the output is empty. - For the Get Fields operation: Outputs a JSON object containing the extracted form fields from the PDF under the
fieldsproperty.
Dependencies
- Requires access to a running instance of the PDF Fill API, reachable via the configured Base URL.
- The node sends HTTP POST requests with multipart/form-data payloads including the PDF file and optional parameters.
- No internal credentials are required, but if the PDF is password protected, the password must be provided.
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 data.
- Password-protected PDFs without the correct password may fail to process.
- Malformed or missing fields in the "Fill" operation can lead to incomplete or failed form filling.
Error messages:
- HTTP errors indicating connection failure or 4xx/5xx responses suggest issues with the API endpoint or request format.
- Errors related to binary data retrieval indicate problems accessing the specified binary property.
- JSON parsing errors may occur if the fields parameter is not properly formatted.
To resolve these:
- Verify the Base URL and ensure the PDF Fill API is accessible.
- Confirm the binary property name matches the incoming data.
- Provide the correct password for protected PDFs.
- Ensure fields are correctly specified with valid names and values.
Links and References
- PDF Fill API Documentation (Replace with actual link if available)
- n8n documentation on working with binary data
- n8n HTTP Request node documentation for understanding HTTP options used.