Actions19
- AI Invoice Parser
- URL/HTML to PDF
- Merge PDF
- Split PDF
- Convert To PDF
- Convert From PDF
- Add Text/Images to PDF
- Fill a PDF Form
- PDF Information & Form Fields
- Compress PDF
- PDF Security
- Rotate PDF Pages
- Delete PDF Pages
- Search in PDF
- Search & Replace Text or Delete
- Barcode Reader
- Barcode Generator
- Make PDF Searchable or Unsearchable
- Upload File
Overview
This node allows users to fill PDF forms by specifying a source PDF file URL and providing field data to populate the form fields. It is useful in scenarios where automated filling of standardized PDF documents is required, such as invoices, contracts, or application forms. For example, you can automatically fill customer information into a PDF invoice template fetched from a URL, then output the filled PDF for further processing or delivery.
Properties
| Name | Meaning |
|---|---|
| Url | The URL of the PDF file to fill. This should point to the source PDF form that needs to be populated. |
| Fields | A collection of field data entries to fill into the PDF form. Each entry includes: - Field Name: The exact name of the form field to fill. - Text: The text content to insert. - Pages: Which pages to fill (default "0" means all). - Font Size: Size of the font. - Font Bold: Whether the font is bold. - Italic: Whether the font is italic. - Strikeout: Whether the font is strikethrough. - Font Underline: Whether the font is underlined. - Font Name or ID: Choose a font from a list or specify an ID. |
| Advanced Options | Additional optional settings: - File Name: Name of the output PDF file. - Webhook URL: A callback URL to receive the output data asynchronously. - Output Links Expiration (In Minutes): How long output links remain valid. - Custom Profiles: JSON string to customize API call properties, e.g., output format. |
Output
The node outputs JSON data representing the result of the PDF form filling operation. This typically includes links or base64-encoded data of the filled PDF document. If a webhook URL is provided, the output may be delivered asynchronously via the callback. Binary data output is not explicitly detailed but may be handled through the output links or base64 encoding depending on custom profiles.
Dependencies
- Requires access to the PDF file via a publicly accessible URL.
- Uses an external PDF processing API service to perform the form filling.
- May require an API key credential configured in n8n to authenticate with the PDF processing service.
- Supports loading fonts and languages dynamically via internal resource loading methods.
Troubleshooting
- Invalid URL or inaccessible PDF: Ensure the provided PDF URL is correct and publicly accessible without authentication.
- Field names mismatch: The field names must exactly match those in the PDF form; otherwise, fields will not be filled.
- Font issues: Specifying unsupported font names or IDs may cause errors or default font usage.
- Webhook callback failures: If using a webhook URL, ensure it is reachable and correctly handles incoming data.
- API limits or authentication errors: Verify API credentials and usage limits with the external PDF service.
Links and References
- PDF.co API Profiles Documentation — for customizing API call options via the "Custom Profiles" property.
- n8n Expressions Documentation — for using expressions in properties like font selection.