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 converts various input file formats into PDF documents. It supports multiple input data types including binary data from previous nodes, base64 encoded strings, and URLs pointing to files. This flexibility makes it useful in workflows where files need to be standardized into PDFs for archiving, sharing, or further processing.

Common scenarios include:

Converting uploaded documents (e.g., Word, images) into PDFs.
Fetching a document from a URL and converting it to PDF.
Processing base64 encoded content received from APIs or other sources.

For example, you might use this node to convert a Word document received as binary data into a PDF before sending it via email or storing it in a document management system.

Properties

Name	Meaning
Input Data Type	How the input file is provided. Options: • Binary Data — Use binary data from a previous node. • Base64 String — Provide base64 encoded content. • URL — Provide a URL to the file to convert.
Binary Property	The name of the binary property containing the file to convert (used when Input Data Type is Binary Data).
Input File Name	The name of the input file including extension. If not provided with binary data, the filename from the binary data will be used. Required for Base64 and URL input types.
Base64 Content	Base64 encoded content of the file to convert (required if Input Data Type is Base64 String).
File URL	URL of the file to convert to PDF (required if Input Data Type is URL).
Output File Name	Desired name for the output PDF file. Defaults to "output.pdf".
Advanced Options	Custom JSON profiles to adjust conversion properties. Users can specify additional options supported by the underlying API to customize the PDF output. For details, see https://dev.pdf4me.com/apiv2/documentation/.

Output

The node outputs the converted PDF file as binary data under the specified output binary property (default naming conventions apply). The json output contains metadata about the operation and the file, typically including the filename and possibly other relevant information.

If the input was binary or base64, the output binary data represents the newly created PDF file. If the input was a URL, the node downloads the file, converts it, and outputs the PDF similarly.

Dependencies

Requires an external PDF conversion service accessible via API.
Needs an API key credential configured in n8n to authenticate requests to the PDF conversion service.
Network access to URLs if using the URL input type.

Troubleshooting

File Not Found or Download Errors: When using URL input, ensure the URL is accessible and publicly reachable or properly authenticated.
Invalid Base64 Content: If providing base64 content, verify that the string is correctly encoded and complete.
Unsupported File Format: The input file must be in a format supported by the conversion service; otherwise, conversion will fail.
Missing Input File Name: For base64 and URL inputs, the input file name including extension is required to determine the file type.
API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
Large Files: Very large files may cause timeouts or memory issues depending on the environment and service limits.