Actions80
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Image Watermark To Image
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- Add Text Watermark To Image
- AI-Invoice Parser
- AI-Process Contract
- AI-Process HealthCard
- Classify Document
- Compress Image
- Compress PDF
- Convert HTML To PDF
- Convert Image Format
- Convert JSON To Excel
- Convert Markdown To PDF
- Convert PDF To Editable PDF Using OCR
- Convert PDF To Excel
- Convert PDF To PowerPoint
- Convert PDF To Word
- Convert To PDF
- Convert URL to PDF
- Convert VISIO
- Convert Word to PDF Form
- Create Images From PDF
- Create PDF/A
- Create Swiss QR Bill
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Split PDF By Barcode
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Extract Attachment From PDF
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Resources
- Extract Table From PDF
- Extract Text By Expression
- Extract Text From Word
- Fill PDF Form
- Find And Replace Text
- Flip Image
- Flatten PDF
- Generate Barcode
- Generate Document Single
- Generate Documents Multiple
- Get Document From Pdf4me
- Get Image Metadata
- Get PDF Metadata
- Split PDF By Swiss QR
- Get Tracking Changes In Word
- Image Extract Text
- Linearize PDF
- Merge Multiple PDFs
- Overlay PDFs
- Parse Document
- Protect PDF
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Remove EXIF Tags From Image
- Repair PDF Document
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Document
- Rotate Image
- Rotate Image By EXIF Data
- Rotate PDF Page
- Sign PDF
- Split PDF By Text
- Split PDF Regular
- Unlock PDF
- Update Hyperlinks Annotation
- Upload File To PDF4me
Overview
The node provides a "Convert To PDF" operation that 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 allows users to convert documents received in different forms into PDFs for easier sharing, archiving, or further processing.
Common scenarios include:
- Converting uploaded Word documents or images (provided as binary data) into PDFs.
- Converting files fetched from external URLs directly into PDFs.
- Processing base64 encoded content (e.g., from APIs or other integrations) into PDF format.
Practical examples:
- A user uploads a DOCX file which is passed as binary data; the node converts it to PDF for standardized output.
- An automation fetches a document URL from an email and converts the linked file to PDF.
- A system receives base64 encoded content of a report and converts it to PDF for storage.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | How the input file is provided. Options: Binary Data (from previous node), Base64 String (base64 encoded content), URL (link to the file). |
| Binary Property | Name of the binary property containing the file to convert (used when Input Data Type is Binary Data). |
| Input File Name | Name of the input file including extension. Optional for binary data input (will use filename from binary if not provided). Required for base64 and URL inputs. |
| 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 | Collection of advanced settings, including "Custom Profiles" where JSON can be used to adjust custom properties for the conversion API call. |
| 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 file as binary data under the specified binary data output name (default "data"). The output includes:
json: Metadata about the conversion result (typically minimal or empty).binary: Contains the PDF file data with the specified output file name.
This allows downstream nodes to access the PDF file either for saving, sending, or further processing.
Dependencies
- Requires an external PDF conversion service accessible via API (implied by references to API calls and profiles).
- Needs proper API authentication configured in n8n credentials (an API key or token).
- Network access to URLs if converting from URL input type.
Troubleshooting
- Missing or incorrect input data: Ensure the input data matches the selected input type (binary, base64, or URL) and required fields like file names are provided.
- Invalid file format or corrupted input: Conversion may fail if the input file is not supported or corrupted.
- API authentication errors: Verify that the API key/token is correctly set up and has permissions.
- Network issues: For URL input, ensure the URL is accessible and returns a valid file.
- Advanced options JSON syntax errors: If using custom profiles, ensure the JSON is well-formed.
Common error messages will typically relate to invalid input, failed API calls, or missing credentials. Resolving involves checking input correctness, credential setup, and network connectivity.
Links and References
- PDF4me API Documentation — for details on custom profiles and advanced options.
- n8n documentation on working with binary data.