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 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 transformation of Word documents (such as contracts, applications, or surveys) into interactive PDF forms for easier distribution and data collection. For example, an HR department could convert employment agreement templates into fillable PDFs to streamline onboarding paperwork.

Properties

Name Meaning
Input Data Type How the input Word document is provided. Options:
• Binary Data — Use Word document from previous node
• Base64 String — Provide Word document content as base64 encoded string
• URL — Provide URL to Word document
Binary Property Name of the binary property containing the Word document (used only if Input Data Type is Binary Data).
Input File Name Name of the input Word file including extension. If not provided when using binary data, filename from binary data will be used. Required for base64 and URL input types.
Base64 Content Base64 encoded content of the Word document (required if Input Data Type is Base64 String).
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 Custom JSON profiles to adjust extra API call properties. Users can specify additional options by providing JSON according to external API documentation.
Binary Data Output Name Custom name for the binary data field in the node's output. Defaults to "data".

Output

The node outputs the converted PDF form as binary data under the specified binary data output name (default "data"). The JSON output contains metadata about the conversion result, while the binary data holds the actual PDF file content ready for further use or download.

If the user sets a custom binary data output name, the PDF binary will be accessible under that name in the output.

Dependencies

  • Requires access to an external PDF conversion API service capable of converting Word documents to PDF forms.
  • Needs an API key or authentication token configured in n8n credentials to authorize requests to the external service.
  • Network access to fetch documents if using URL input type.

Troubleshooting

  • Missing or invalid input file: Ensure the Word document is correctly provided either as binary data, valid base64 string, or accessible URL.
  • Incorrect file name or extension: The input file name must include the correct extension (e.g., .docx) especially when using base64 or URL inputs.
  • API authentication errors: Verify that the API key or authentication token is properly set up in n8n credentials.
  • Network issues fetching URL: If using URL input, ensure the URL is reachable and publicly accessible or accessible from the n8n environment.
  • Invalid advanced options JSON: When using custom profiles, ensure the JSON syntax is correct and matches the external API specification.

Links and References

Discussion