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 operation converts a Word document into a fillable PDF form. It supports multiple input methods for the Word document, including binary data from a previous node, a base64-encoded string, or a URL pointing to the document. The output is a PDF file with form fields that can be filled electronically.

This operation is useful in scenarios where users need to automate the creation of interactive PDF forms from existing Word documents, such as generating application forms, contracts, surveys, or any document requiring user input in a standardized format.

Practical examples:

Automatically converting a Word template of a job application into a PDF form that candidates can fill out digitally.
Transforming a Word-based survey into a PDF form for easier distribution and data collection.
Creating fillable contract forms from Word documents for electronic signing workflows.

Properties

Name	Meaning
Input Data Type	How the input Word document is provided. Options: • Binary Data (from previous node) • Base64 String (base64 encoded content) • URL (link to the Word document)
Binary Property	Name of the binary property containing the Word document (used when Input Data Type is Binary Data).
Input File Name	Name of the input Word file including extension. Optional if using binary data; required if using base64 or URL input types.
Base64 Content	Base64 encoded content of the Word document (required if Input Data Type is Base64 String).
Input File Name (Base64/URL)	Name of the input Word file including extension (required if Input Data Type is Base64 or URL).
File URL	URL of the Word document to convert (required if Input Data Type is URL).
Output File Name	Desired name for the output PDF form file. Defaults to "word_to_pdf_form_output.pdf".
Advanced Options	Collection of optional advanced settings. For example, custom profiles in JSON format to adjust API call properties. Users can refer to external API documentation for available profile options.
Binary Data Output Name	Custom name for the binary data field in the node's output. Defaults to "data".

Output

The node outputs a single item containing the converted PDF form as binary data. The binary data field name can be customized via the "Binary Data Output Name" property (default is "data"). The output binary data represents the fillable PDF form generated from the input Word document.

No additional JSON structure details are exposed beyond the binary content representing the PDF form.

Dependencies

Requires access to an external PDF conversion service API capable of converting Word documents to fillable PDF forms.
Requires appropriate API authentication credentials configured in n8n (e.g., an API key or token).
Network access to fetch documents if using URL input type.

Troubleshooting

Common issues:
- Incorrect or missing input file name when using base64 or URL input types may cause conversion failure.
- Invalid or inaccessible URL will result in errors fetching the Word document.
- Malformed base64 content will cause decoding errors.
- Missing or invalid API credentials will prevent successful conversion.
Error messages:
- Errors related to file not found or inaccessible URL indicate checking the URL or network connectivity.
- Authentication errors suggest verifying API credentials setup.
- Conversion errors might require validating the input Word document format and content.
To resolve issues, ensure all required inputs are correctly provided, credentials are valid, and the external service is reachable.

Links and References

PDF4me API Documentation — for advanced profile options and detailed API capabilities related to document conversion and customization.